Method for installing a fixed wireless access link with alignment signals

ABSTRACT

An intelligent backhaul system is disclosed for deployment in the presence of existing radio systems. A backhaul system for co-channel deployment with existing licensed and unlicensed wireless networks, including conventional cellular backhaul radios, Common Carrier Fixed Point-to-Point Microwave Service, Private Operational Fixed Point-to-Point Microwave Service and other FCC 47 C.F.R. § 101 licensed microwave networks is disclosed. Processing and network elements to manage and control the deployment and management of backhaul of radios that connect remote edge access networks to core networks in a geographic zone which co-exist with such existing systems or other sources of interference within a radio environment are also disclosed.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a Continuation of U.S. application Ser. No.15/403,090, filed on Jan. 10, 2017, which is Continuation of U.S.application Ser. No. 15/084,867, filed on Mar. 30, 2016, now U.S. Pat.No. 9,577,733, which is a Continuation of U.S. application Ser. No.14/839,018, filed on Aug. 28, 2015, now U.S. Pat. No. 9,325,398, whichis a Continuation of U.S. application Ser. No. 13/934,175,filed on Jul.2, 2013, now U.S. Pat. No. 9,179,240, which is a Continuation of U.S.application Ser. No. 13/371,346, filed on Feb. 10, 2012, U.S. Pat. No.8,502,733, the disclosures of which are hereby incorporated herein byreference in their entireties.

The present application is also related to U.S. patent application Ser.No. 13/212,036, filed on Aug. 17, 2011, now U.S. Pat. No. 8,238,318,U.S. patent application Ser. No. 13/371,366, filed on Feb. 10, 2012, nowU.S. Pat. No. 8,311,023, U.S. patent application Ser. No. 13/645,472,filed on Oct. 4, 2012, now U.S. Pat. No. 8,811,365, U.S. patentapplication Ser. No. 14/197,158, filed on Mar. 4, 2014, now U.S. Pat.No. 8,928,542, U.S. patent application Ser. No. 14/199,734, filed onMar. 6, 2014, now U.S. Pat. No. 8,872,715, U.S. patent application Ser.No. 14/559,859, filed on Dec. 3, 2014, U.S. Provisional PatentApplication No. 61/857,661, filed on Jul. 23, 2013, U.S. patentapplication Ser. No. 14/151,190, filed on Jan. 9, 2014, now U.S. Pat.No. 8,982,772, U.S. patent application Ser. No. 14/608,024, filed onJan. 28, 2015, U.S. patent application Ser. No. 15/050,009, filed onFeb. 22, 2016, U.S. Provisional Patent Application No. 62/130,100, filedon Mar. 9, 2015,U.S. Provisional Patent Application No. 62/135,573,filed on Mar. 19, 2015, U.S. patent application Ser. No. 14/337,744,filed on Jul. 22, 2014, now U.S. Pat. No. 9,055,463, U.S. ProvisionalPatent Application No. 61/910,194, filed on Nov. 29, 2013, U.S. patentapplication Ser. No. 14/498,959, filed on Sep. 26, 2014, now U.S. Pat.No. 9,049,611, U.S. patent application Ser. No. 14/688,550, filed onApr. 16, 2015, U.S. patent application Ser. No. 15/060,013, filed onMar. 3, 2016, U.S. patent application Ser. No. 14/686,674, filed on Apr.14, 2015, now U.S. Pat. No. 9,282,560, U.S. patent application Ser. No.14/988,578, filed on Jan. 5, 2016, U.S. patent application Ser. No.14/098,456, filed on Dec. 5, 2013, now U.S. Pat. No. 8,989,762, U.S.patent application Ser. No. 14/502,471, filed on Sep. 30, 2014, U.S.patent application Ser. No. 14/624,365, filed on Feb. 17, 2015, U.S.patent application Ser. No. 14/666,294, filed on Mar. 23, 2015, U.S.patent application Ser. No. 13/536,927, filed on Jun. 28, 2012, now U.S.Pat. No. 8,467,363, U.S. patent application Ser. No. 13/898,429, filedon May 20, 2013, now U.S. Pat. No. 8,824,442, U.S. patent applicationSer. No. 14/336,958, filed on Jul. 21, 2014, now U.S. Pat. No.9,001,809, U.S. patent application Ser. No. 14/632,624, filed on Feb.26, 2015, now U.S. Pat. No. 9,178,558, and U.S. patent application Ser.No. 14/837,797, filed on Aug. 26, 2015, the disclosures of which arehereby incorporated herein by reference in their entireties.

BACKGROUND

1. Field

The present disclosure relates generally to data networking and inparticular to a backhaul system for co-channel deployment with existinglicensed and unlicensed wireless networks, and to processing and networkelements to manage and control the deployment and management of backhaulradios that connect remote edge access networks to core networks in ageographic zone which co-exist with the existing wireless networks.

2. Related Art

Data networking traffic has grown at approximately 100% per year forover 20 years and continues to grow at this pace. Only transport overoptical fiber has shown the ability to keep pace with thisever-increasing data networking demand for core data networks. Whiledeployment of optical fiber to an edge of the core data network would beadvantageous from a network performance perspective, it is oftenimpractical to connect all high bandwidth data networking points withoptical fiber at all times. Instead, connections to remote edge accessnetworks from core networks are often achieved with wireless radio,wireless infrared, and/or copper wireline technologies.

Radio, especially in the form of cellular or wireless local area network(WLAN) technologies, is particularly advantageous for supportingmobility of data networking devices. However, cellular base stations orWLAN access points inevitably become very high data bandwidth demandpoints that require continuous connectivity to an optical fiber corenetwork.

When data aggregation points, such as cellular base station sites, WLANaccess points, or other local area network (LAN) gateways, cannot bedirectly connected to a core optical fiber network, then an alternativeconnection, using, for example, wireless radio or copper wirelinetechnologies, must be used. Such connections are commonly referred to as“backhaul.”

Many cellular base stations deployed to date have used copper wirelinebackhaul technologies such as T1 , E1, DSL, etc. when optical fiber isnot available at a given site. However, the recent generations of HSPA+and LTE cellular base stations have backhaul requirements of 100 Mb/s ormore, especially when multiple sectors and/or multiple mobile networkoperators per cell site are considered. WLAN access points commonly havesimilar data backhaul requirements. These backhaul requirements cannotbe practically satisfied at ranges of 300 m or more by existing copperwireline technologies. Even if LAN technologies such as Ethernet overmultiple dedicated twisted pair wiring or hybrid fiber/coax technologiessuch as cable modems are considered, it is impractical to backhaul atsuch data rates at these ranges (or at least without adding intermediaterepeater equipment). Moreover, to the extent that such special wiring(i.e., CAT 5/6 or coax) is not presently available at a remote edgeaccess network location; a new high capacity optical fiber isadvantageously installed instead of a new copper connection.

Rather than incur the large initial expense and time delay associatedwith bringing optical fiber to every new location, it has been common tobackhaul cell sites, WLAN hotspots, or LAN gateways from offices,campuses, etc. using microwave radios. An exemplary backhaul connectionusing the microwave radios 132 is shown in FIG. 1. Traditionally, suchmicrowave radios 132 for backhaul have been mounted on high towers 112(or high rooftops of multi-story buildings) as shown in FIG. 1, suchthat each microwave radio 132 has an unobstructed line of sight (LOS)136 to the other. These microwave radios 132 can have data rates of 100Mb/s or higher at unobstructed LOS ranges of 300 m or longer withlatencies of 5 ms or less (to minimize overall network latency).

Traditional microwave backhaul radios 132 operate in a Point to Point(PTP) configuration using a single “high gain” (typically >30 dBi oreven >40 dBi) antenna at each end of the link 136, such as, for example,antennas constructed using a parabolic dish. Such high gain antennasmitigate the effects of unwanted multipath self-interference or unwantedco-channel interference from other radio systems such that high datarates, long range and low latency can be achieved. These high gainantennas however have narrow radiation patterns.

Furthermore, high gain antennas in traditional microwave backhaul radios132 require very precise, and usually manual, physical alignment oftheir narrow radiation patterns in order to achieve such highperformance results. Such alignment is almost impossible to maintainover extended periods of time unless the two radios have a clearunobstructed line of sight (LOS) between them over the entire range ofseparation. Furthermore, such precise alignment makes it impractical forany one such microwave backhaul radio to communicate effectively withmultiple other radios simultaneously (i.e., a “point to multipoint”(PMP) configuration).

In wireless edge access applications, such as cellular or WLAN, advancedprotocols, modulation, encoding and spatial processing across multipleradio antennas have enabled increased data rates and ranges for numeroussimultaneous users compared to analogous systems deployed 5 or 10 yearsago for obstructed LOS propagation environments where multi path andco-channel interference were present. In such systems, “low gain”(usually <6 dBi) antennas are generally used at one or both ends of theradio link both to advantageously exploit multipath signals in theobstructed LOS environment and allow operation in different physicalorientations as would be encountered with mobile devices. Althoughimpressive performance results have been achieved for edge access, suchresults are generally inadequate for emerging backhaul requirements ofdata rates of 100 Mb/s or higher, ranges of 300 m or longer inobstructed LOS conditions, and latencies of 5 ms or less.

In particular, “street level” deployment of cellular base stations, WLANaccess points or LAN gateways (e.g., deployment at street lamps, trafficlights, sides or rooftops of single or low-multiple story buildings)suffers from problems because there are significant obstructions for LOSin urban environments (e.g., tall buildings, or any environments wheretall trees or uneven topography are present).

FIG. 1 illustrates edge access using conventional unobstructed LOS PTPmicrowave radios 132. The scenario depicted in FIG. 1 is common for many2^(nd) Generation (2G) and 3^(rd) Generation (3G) cellular networkdeployments using “macrocells”. In FIG. 1, a Cellular Base TransceiverStation (BTS) 104 is shown housed within a small building 108 adjacentto a large tower 112. The cellular antennas 116 that communicate withvarious cellular subscriber devices 120 are mounted on the towers 112.The PTP microwave radios 132 are mounted on the towers 112 and areconnected to the BTSs 104 via an nT1 interface. As shown in FIG.1 byline 136, the radios 132 require unobstructed LOS.

The BTS on the right 104 a has either an nT1 copper interface or anoptical fiber interface 124 to connect the BTS 104 a to the Base StationController (BSC) 128. The BSC 128 either is part of or communicates withthe core network of the cellular network operator. The BTS on the left104 b is identical to the BTS on the right 104 a in FIG. 1 except thatthe BTS on the left 104 b has no local wireline nT1 (or optical fiberequivalent) so the nT1 interface is instead connected to a conventionalPTP microwave radio 132 with unobstructed LOS to the tower on the right112 a. The nT1 interfaces for both BTSs 104 a, 104 b can then bebackhauled to the BSC 128 as shown in FIG. 1.

As described above, conventional microwave backhaul radios have used“high gain” (typically >30 dBi or even >40 dBi) to achieve desiredcombinations of high throughput, long range and low latency in bridgingremote data networks to core networks for unobstructed line of sight(LOS) propagation conditions. Because of their very narrow antennaradiation patterns and manual alignment requirements, these conventionalmicrowave backhaul radios are completely unsuitable for applicationswith remote data network backhaul in obstructed LOS conditions, such asdeployment on street lamps, traffic lights, low building sides orrooftops, or any fixture where trees, buildings, hills, etc., whichsubstantially impede radio propagation from one point to another.

Additionally, such conventional microwave backhaul radios typically havelittle or no mechanism for avoiding unwanted interference from otherradio devices at the same channel frequency (other than the narrownessof their radiation patterns). Thus, users of such equipment are oftenskeptical of deployment of such conventional backhaul radios forcritical applications in unlicensed spectrum bands. Even for commonlicensed band deployments, such as under the United States FederalCommunications Commission (FCC) 47 C.F.R. § 101 rules, conventionalbackhaul radios are typically restricted to a particular channelfrequency, channel bandwidth and location placement based on a manualregistration process carried out for each installation. This is slow,inefficient, and error prone as well as wasteful of spectrum resourcesdue to underutilization, even with the undesirable restriction ofunobstructed LOS conditions.

Furthermore, once deployed in the field, conventional microwave backhaulradios are typically islands of connectivity with little or nocapability to monitor the spectrum usage broadly at the deploymentlocation or coordinate with other radios in the vicinity to optimallyuse spectrum resources.

FIG. 2 illustrates an exemplary deployment of multiple conventionalbackhaul radios (CBRs) 132 as discrete point to point (PTP) links 204 tobridge remote data access networks (ANs) 208 to a private core network(PCN) 212. Each link 204 requires unobstructed LOS propagation and islimited to a single PTP radio configuration. To the extent that multiplelinks originate from a common location, the CBRs 132 at such locationrequire spatial and directional separation if co-channel operation isused.

Typically, the operator of the PCN 212 will use an element managementsystem (EMS) 216 specific to particular CBRs 132 to monitor deployed andconfigured CBR links within the PCN 212. Often, an EMS 216 allows faultmonitoring, configuration, accounting, performance monitoring andsecurity key management (FCAPS) for the CBRs 132 within the PCN 212.However, such a conventional EMS 216 does not dynamically modifyoperational policies or configurations at each CBR 132 in response tomutual interactions, changing network loads, or changes in the radiospectrum environment in the vicinity of the deployed CBRs 132.Furthermore, such an EMS 216 is typically isolated from communicationswith or coordination amongst other EMSs at other PCNs (not shown) thatmay be overlapping geographically from a radio spectrum perspective.

As a result of the foregoing deficiencies with conventional backhaulradios and conventional approaches to obstructed line of sight systems,there exists no practical approach to the deployment, monitoring andoperation of obstructed non-line of sight systems in the presence ofunlicensed or licensed conventional backhaul radios or other licensedservices according to 47 Code of Federal Regulations (C.F.R.) § 101within the same operational bands. Exemplary 47 C.F.R. § 101 systemsinclude Common Carrier Fixed Point to Point Microwave Service andPrivate Operational Fixed Point-to-Point Microwave Service andassociated bands as described, for example, in 47 C.F.R. § 101.101.Further, such deficiencies prevent the rapid deployment of new backhaulradios configured for co-channel operation with these systems, includingconventional backhaul radio networks and other 47 C.F.R. § 101 systems.

SUMMARY

The following summary of the invention is included in order to provide abasic understanding of some aspects and features of the invention. Thissummary is not an extensive overview of the invention and as such it isnot intended to particularly identify key or critical elements of theinvention or to delineate the scope of the invention. Its sole purposeis to present some concepts of the invention in a simplified form as aprelude to the more detailed description that is presented below.

In copending U.S. patent application Ser. No. 13/212,036, entitledIntelligent Backhaul Radio, filed Aug. 17, 2011, the entirety of whichis hereby incorporated by reference, the present inventor disclosedbackhaul radios that are compact, light and low power for street levelmounting, operate at 100 Mb/s or higher at ranges of 300 m or longer inobstructed LOS conditions with low latencies of 5 ms or less, cansupport PTP and PMP topologies, use radio spectrum resources efficientlyand do not require precise physical antenna alignment. Radios with suchexemplary capabilities are referred to as Intelligent Backhaul Radios(IBRs).

These IBRs overcome the limitation of obstructed LOS operation andenable many desirable capabilities such as, for example only, monitoringof spectrum activity in the vicinity of the deployment and activelyavoiding or mitigating co-channel interference. To fully utilize theseand other capabilities of the IBRs, it is advantageous to manage andcontrol multiple IBRs within a geographic zone collectively as an“Intelligent Backhaul System” (or IBS).

In co-pending U.S. patent application Ser. No. 13/271,051, entitledIntelligent Backhaul System, filed Oct. 11, 2011, the entirety of whichis hereby incorporated by reference, the present inventor disclosed anintelligent backhaul system (IBS) that includes a plurality ofintelligent backhaul radios and a server in communication with anintelligent backhaul management system agent within at least one of theplurality of intelligent backhaul radios. The server is configured tomanage or control at least one of the plurality of intelligent backhaulradios.

The IBRs and the IBS can be utilized to aid in the determination,deployment and management of IBR operational parameters in the samebands of operation as existing CBRs or other radios to which or fromwhich interference is undesirable or forbidden (e.g., within specific 47C.F.R. § 101 licensed bands). In some embodiments, such deployment mayinclude co-channel operation with CBRs or other systems includingparticularly within specific 47 C.F.R. § 101 licensed bands systems,such as Common Carrier Fixed Point to Point Microwave Service andPrivate Operational Fixed Point-to-Point Microwave Service andassociated bands.

Information stored within or obtained by the IBS or other networkelements can be used to determine or aid in the determination of IBRoperational parameters that allow co-band or co-channel operation withmanageable interference impact to and from CBRs or other services withina geographic zone, or within a known radio frequency propagationdistance.

Exemplary IBR operational parameters include but are not limited to: theselection operational frequencies; the modification of transmitterantenna patterns; the modifying or selection of antenna polarization orspatial patterns; the selection of specific antennas from a set ofavailable antennas; the selection of transmission nulls reducing theinterference impinging upon other systems; the selection of receive ortransmission digital beam forming weights, or algorithmic beam formingconstraints; the physical movement, placement, alignment, oraugmentation of one or more antenna elements, or antenna arrays byelectrical, or electromechanical control or by a request for manualadjustment or augmentation during or after installation; and themodification of transmission power; and the selection of interferencemargin values for the reduction of the risk in interfering existingsystems.

In one embodiment, the determination of the IBR operational parametersis performed utilizing an algorithm based at least in part on known CBRlocations and radiation parameters that are stored, for example, in theUniversal Licensing System (ULS) operated by the Federal CommunicationsCommission (FCC), or in other public or private databases.

In one embodiment, ULS information and associated radiation parameters,in combination with radio frequency propagation models are utilized todetermine the level to which operation of an IBR under various IBRoperational parameters would interfere with one or more licensed 47C.F.R. § 101 services, including Common Carrier Fixed Point to PointMicrowave Service and Private Operational Fixed Point-to-Point MicrowaveService within designated bands.

In one embodiment, reports of received signals are provided by the IBRs,optionally in combination with existing IBR operational parameters, tothe Intelligent Backhaul Radio Management System (IBMS) for use in IBRoperational parameter determination. Such reports may be stored by theIBMS and used alone or in combination with CBR radiation parameterinformation from public or private databases to perform IBR operationalparameter selection.

Further embodiments may include an iterative method. For example, theIBRs may report received spectral measurements and configurationparameters to the IBMS, which performs selection of some or all for theoperation parameters, and passes said parameters to respective IBRs. TheIBRs may then perform additional or refined scanning, or initialoperation, prior to the determination of the IBR operational parameters.

In one embodiment, a remote end IBR (RE-IBR) is configured to operatewith an aggregation end IBR (AE-IBR) on one or more frequency channelswhich are co-channel with a time division duplexed (TDD) CBR. In thisembodiment, the AE-IBR has a wired Ethernet connection to the IMBS. TheRE-IBR connects to the IBMS utilizing an out of band data link in theform of a cellular data link during configuration, which may be a mobilephone having a Wi-Fi connection to the RE-IBR (i.e., the phone is actingas a mobile hot spot) or utilizing a Wi-Fi direct connection. Uponinitiating the configuration process, the respective IBRs perform a scanof their receive channels to detect existing CBRs. The IBRs then reporttheir respective antenna configurations and scan results to the IBMS.The IMBS, in one embodiment, determines, assuming another channel maynot be used, the level of interference the CBR will receive. Theinterference is determined utilizing IBR effective antenna patternadjustments and, optionally, associated information retrieved from adatabase of CBR parameters. In one embodiment, the effective antennapattern adjustment includes the use of a transmission beam nulling fromthe required one or more IBRs to further reduce the interference levelswhich may be received at the CBR, while maintaining a minimum requiredperformance between the respective IBRs. In some embodiments, aninterference margin is calculated. The interference margin can used asan additional reduction of the required interference to the target CBR.The interference margin may be based on a fixed amount, a level ofuncertainty of the predicted interference, an amount based upon thereliability or predicted accuracy of interference calculations, or basedupon using or the availability of or specific values of CBR antenna andoperating transmission parameters retrieved from a database.

In some embodiments, the RE-IBRs and AE-IBRs may operate on channels forwhich no interference is detected, but are within a predetermineddistance of a CBR. The distance may be determined based on thegeographic location of each IBR and the CBR (e.g., the location of theCBR determined by accessing the FCC ULS database). In such situations,an interference margin value, or other operational constraint value, maybe utilized by the IBMS based upon propagation models to further reducethe likelihood of interfering with the CBR.

In some embodiments, co-existence of IBRs with FDD (frequency divisionduplex) CBRs may be required. In these embodiments, interference marginsor operational transmission constraints may be calculated. An exemplaryconstraint is transmission beam nulling. In this example, during a scanprocedure, the values related to transmission beam nulling may bedetermined.

In some embodiments, received signals transmitted from a CBR operatingin FDD are detected during a scan procedure at an IBR. However, the IBRto IBR link, in one deployment, is configured to operate on the specificFDD paired frequency channel used for receiving by the FDD CBR asdetermined by the IMBS and FCC database records. In this embodiment,transmission beam nulling weights or constraints may be determined basedupon the received signals in the paired channel, despite the frequencydifference for the transmission channel. Such calculations may utilizepropagation modeling to determine interference levels, reportedmeasurements by the IBR to determine the level of frequency flat fading,and database values related to CBR parameters. These calculationsinvolve a constrained transmission beam forming calculation. Forexample, an interference margin may be included based at least in partupon the determined level of flat fading of the scanned signal on thepaired band.

It will be appreciated that many of the processes and/or process stepsdescribed above may be performed by the IBMS. It will also beappreciated that these processes and/or process steps may be performedby one or more servers or processing nodes operating within the IBMS, onbehalf of the IBMS, or otherwise in association with the IBMS toaccomplish the processes or steps, including, for example, IBRs, IBCs,mobile IBR configuration devices, smart phones, tables, and cloudcomputing resources.

According to one embodiment of the invention, an intelligent backhaulradio is disclosed that includes a plurality of receive RF chains; oneor more transmit RF chains; an antenna array comprising a plurality ofdirective gain antenna elements, wherein each directive gain antennaelement is couplable to at least one receive RF or transmit RF chain;and an interface bridge configured to couple the intelligent backhaulradio to a data network, the interface bridge comprising one or moreEthernet interfaces to couple the interface bridge to the data network,wherein the intelligent backhaul radio is configured to scan a pluralityof radio frequency channels for the presence of radio signalstransmitted from one or more point to point microwave systems togenerate scan data, and wherein the intelligent backhaul radio comprisesat least one adjustable network parameter that is adjustable based onthe scan data, wherein the at least one network parameter is adjusted toreduce a potential of interference of the intelligent backhaul radiowith the one or more point to point microwave systems, wherein theintelligent backhaul radio is a first intelligent backhaul radio, andwherein the adjusting the at least one network parameter comprises oneor more of: selecting a frequency channel utilized between the firstintelligent backhaul radio and a second intelligent backhaul radio;adjusting the effective radiation pattern of the first intelligentbackhaul radio; selecting one or more of the plurality of directive gainantenna elements; and adjusting the physical configuration orarrangement of the one or more of the plurality of directive gainantenna elements.

The intelligent backhaul radio may include an intelligent backhaulcontroller. The intelligent backhaul radio may include an intelligentbackhaul management system agent. The intelligent backhaul radio mayinclude a wireless adapter.

The intelligent backhaul radio may be further configured to generate ascan report based on the scan data and transmit the scan report to aserver.

The signals may include a signal licensed by the Federal CommunicationsCommission (FCC) under 47 Code of Federal Regulations (CFR) section 101as a common carrier fixed point-to-point microwave service or as aprivate operational fixed point-to-point microwave service.

Adjusting the effective radiation pattern may include one or more of:steering the effective radiation pattern in elevation; and steering theeffective radiation pattern in azimuth.

Adjusting the effective radiation pattern may include calculatingdigital beam former weights based upon at least one constraint relatedto the potential of interference; and applying the digital beam formerweights.

The constraint may be selected from the group consisting of: propertiesrelated to or derived from said scan result; a direction in which signaltransmission is to be limited; parameters which reduce the potential forinterfering with said one or more point to point microwave systems;parameters which increase the likelihood of said first and said secondinternet backhaul radios meeting performance goals with respect to aninterposed wireless communication link; a restriction of use of specifictransceivers or specific antennas of a plurality of transceivers orantennas; a use of specific polarizations for transmission; attributesof a collective transmission radiation pattern associated with aplurality of transmitters; a frequency or geometric translation of beamforming weights between receiver weights and transmitter weights; basedupon a change in antennas used or selected; based upon a change inoperating frequency; and combinations thereof.

The scan report may include one more selected from the group consistingof: the location of said first IBR; the latitude and longitudinalcoordinates of one or more IBRs; configuration information related tothe first IBR; capability information related to the first IBR; atransmission power capability of said first IBR; operating frequencycapability of said first IBR; antenna property information related toone or more antenna for use in reception or transmission by said firstIBR; received signal parameters or demodulated information from anotherinternet backhaul radio; received signal parameters from a receivedpoint to point microwave system; and combinations thereof.

The intelligent backhaul radio may be further configured to assessperformance after adjustment of the at least one adjustable networkparameter.

The intelligent backhaul radio may be a first intelligent backhaulradio, and the performance may be assessed by one or more selected fromthe group consisting of: performing additional scans; performingadditional scans with specific search criteria; performing additionalscans with limitations in frequency, azimuth, elevation, or time;performing additional scans with a modified antenna selectionconfiguration; performing additional scans using antennas intended fortransmission during normal operation for reception during the additionalscanning process; performing transmission of a signal from the firstintelligent backhaul radio to a second intelligent backhaul radio,receiving a signal from the second intelligent backhaul radio by thefirst intelligent backhaul radio.

The intelligent backhaul radio may be a first intelligent backhaulradio, and the first intelligent backhaul radio may be configured toalign the antenna array with a second intelligent backhaul radio priorto the scan based on at least one criterion.

The at least one criterion may be based at least in part upon a signaltransmitted from the second intelligent backhaul radio.

The at least one criterion may include a GPS location and a compassdirection.

According to another embodiment of the invention, an intelligentbackhaul system is disclosed that includes an intelligent backhaul radiohaving a plurality of receive RF chains; one or more transmit RF chains;an antenna array comprising a plurality of directive gain antennaelements, wherein each directive gain antenna element is couplable to atleast one receive RF or transmit RF chain; and an interface bridgeconfigured to couple the intelligent backhaul radio to a data network,the interface bridge comprising one or more Ethernet interfaces tocouple the interface bridge to the data network, wherein the intelligentbackhaul radio is configured to scan a plurality of radio frequencychannels for the presence of radio signals transmitted from one or morepoint to point microwave systems to generate scan data, and wherein theintelligent backhaul radio comprises at least one adjustable networkparameter that is adjustable based on the scan data; and a server incommunication with the intelligent backhaul radio, wherein the server isconfigured to receive the scan data from the intelligent backhaul radio,wherein the at least one network parameter is adjusted to reduce thepotential of interference of the intelligent backhaul radio with the oneor more point to point microwave systems, wherein the intelligentbackhaul radio is a first intelligent backhaul radio, and wherein theadjusting the at least one network parameter includes one or more of:selecting a frequency channel utilized between the first intelligentbackhaul radio and a second intelligent backhaul radio; adjusting theeffective radiation pattern of the first intelligent backhaul radio;selecting one or more of the plurality of directive gain antennaelements; and adjusting the physical configuration or arrangement of theone or more of the plurality of directive gain antenna elements.

The server may be configured to store data received from the intelligentbackhaul radio.

The system may further include one or more intelligent backhaulcontrollers.

The intelligent backhaul radio may include an intelligent backhaulcontroller.

The intelligent backhaul radio may include an intelligent backhaulmanagement system agent.

The server may be at least one of a private server and a global server.

The intelligent backhaul radio may include a wireless adapter.

The intelligent backhaul radio may be further configured to generate ascan report based on the scan data, and wherein the server is configuredto receive the scan report.

The server may utilize the scan data to identify the at least onenetwork parameter to be adjusted.

The signals may include a signal licensed by the Federal CommunicationsCommission (FCC) under 47 Code of Federal Regulations (CFR) section 101as a common carrier fixed point-to-point microwave service or as aprivate operational fixed point-to-point microwave service.

The scan data may be analyzed by the server to determine a potential ofinterference of the intelligent backhaul radio with the one or morepoint to point microwave systems.

The server may perform a mathematical modeling of the radio propagationof one or more potentially interfering signals from the intelligentbackhaul radio to the one or more point to point microwave systems.

Adjusting the effective radiation pattern may include one or more of:steering the effective radiation pattern in elevation; and steering theeffective radiation pattern in azimuth.

Adjusting the effective radiation pattern may include calculatingdigital beam former weights based upon at least one constraint relatedto the potential of interference; and applying the digital beam formerweights.

The constraint may be selected from the group consisting of: propertiesrelated to or derived from said scan result; a direction in which signaltransmission is to be limited; parameters which reduce the potential forinterfering with said one or more point to point microwave systems;parameters which increase the likelihood of said first and said secondinternet backhaul radios meeting performance goals with respect to aninterposed wireless communication link; a restriction of use of specifictransceivers or specific antennas of a plurality of transceivers orantennas; a use of specific polarizations for transmission; attributesof a collective transmission radiation pattern associated with aplurality of transmitters; a frequency or geometric translation of beamforming weights between receiver weights and transmitter weights; basedupon a change in antennas used or selected; based upon a change inoperating frequency; and combinations thereof.

The mathematical modeling may be based on the scan data.

The scan report may include one more selected from the group consistingof: the location of said first IBR; the latitude and longitudinalcoordinates of one or more IBRs; configuration information related tothe first IBR; capability information related to the first IBR; atransmission power capability of said first IBR; operating frequencycapability of said first IBR; antenna property information related toone or more antenna for use in reception or transmission by said firstIBR; received signal parameters, or demodulated information from anotherinternet backhaul radio; received signal parameters from a receivedpoint to point microwave system; and combinations thereof.

The intelligent backhaul radio may be further configured to assessperformance after adjustment of the at least one adjustable networkparameter.

The intelligent backhaul radio may be a first intelligent backhaulradio, and the performance may be assessed by one or more selected fromthe group consisting of: performing additional scans; performingadditional scans with specific search criteria; performing additionalscans with limitations in frequency, azimuth, elevation, or time;performing additional scans with a modified antenna selectionconfiguration; performing additional scans using antennas intended fortransmission during normal operation for reception during the additionalscanning process; performing transmission of a signal from the firstintelligent backhaul radio to a second intelligent backhaul radio;receiving a signal from the second intelligent backhaul radio by thefirst intelligent backhaul radio.

The intelligent backhaul radio may be a first intelligent backhaulradio, and the first intelligent backhaul radio may be configured toalign the antenna array with a second intelligent backhaul radio priorto the scan based on at least one criterion.

The at least one criterion may be based at least in part upon a signaltransmitted from the second intelligent backhaul radio. The at least onecriterion may include a GPS location and a compass direction. The systemmay further include an installation assisting device, and theinstallation assisting device may determine the GPS location and thecompass direction.

The server may be coupled with a database, and the database may includeinformation related to one or more existing point to point microwavesites.

The information may include one or more selected from the groupconsisting of: radio service group; fixed transmit location details;latitude and longitude of one or more existing point to point microwavesites; street address of one or more existing point to point microwavesites; site elevation; antenna elevation; transmitter antenna height;polarization; beam width; antenna pointing azimuth and elevation angle;antenna gain; transmitter power or equivalent isotropically radiatedpower (EIRP); frequency of operation or frequency tolerance; emissiondesignator; equipment modulation type and rate; and equipmentmanufacturer.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated into and constitute apart of this specification, illustrate one or more examples ofembodiments and, together with the description of example embodiments,serve to explain the principles and implementations of the embodiments.

FIG. 1 is an illustration of conventional point to point (PTP) radiosdeployed for cellular base station backhaul with unobstructed line ofsight (LOS).

FIG. 2 is an illustration of an exemplary deployment of conventionalbackhaul radios.

FIG. 3 is an illustration of intelligent backhaul radios (IBRs) deployedfor cellular base station backhaul with obstructed LOS according to oneembodiment of the invention.

FIG. 4 is an exemplary deployment of an intelligent backhaul system(IBS) according to one embodiment of the invention.

FIG. 5 is a block diagram of an IBR according to one embodiment of theinvention.

FIG. 6 is a block diagram of an IBR according to one embodiment of theinvention.

FIG. 7 is a block diagram of an intelligent backhaul controller (IBC)according to one embodiment of the invention.

FIG. 8A is a perspective view of an IBR including antenna array geometryaccording to one embodiment of the invention.

FIG. 8B is a perspective view of an IBR including antenna array geometryaccording to one embodiment of the invention.

FIG. 9 illustrates exemplary deployment of intelligent backhaul radios(IBRs) deployed for cellular base station backhaul with obstructed LOSin the presence of an existing exemplary deployment of conventionalbackhaul radios deployed for cellular base station backhaul withunobstructed line of sight (LOS) according to one embodiment of theinvention.

FIG. 10 illustrates an exemplary deployment of intelligent backhaulradios (IBRs) deployed for cellular base station backhaul withobstructed LOS in the presence of an existing exemplary deployment ofconventional backhaul radios deployed for cellular base station backhaulwith unobstructed line of sight (LOS) according to one embodiment of theinvention.

FIG. 11 illustrates an exemplary deployment of an intelligent backhaulsystem (MS) in the presence of an existing exemplary deployment ofconventional backhaul radios according to one embodiment of theinvention.

FIG. 12 illustrates a normalized antenna gain relative to an angle frombore utilizing an exemplary antenna system.

FIG. 13A is a table of a partial listing for the frequency availabilityfor specific radio services 47 C.F.R. § 101.101.

FIG. 13B illustrates an exemplary deployment for occupancy of servicesin the 3700 to 4200 MHZ frequency band for conventional cellularbackhaul radios or other services as licensed under 47 C.F.R. § 101 andlisted in the FCC Universal Licensing System.

FIG. 14 is a flow chart illustrating an IBR installation processaccording to one embodiment of the present invention.

FIG. 15 is a flow chart illustrating selection of IBR configurationparameters according to one embodiment of the present invention.

DETAILED DESCRIPTION

FIG. 3 illustrates deployment of intelligent backhaul radios (IBRs) inaccordance with an embodiment of the invention. As shown in FIG. 3, theIBRs 300 are deployable at street level with obstructions such as trees304, hills 308, buildings 312, etc. between them. The IBRs 300 are alsodeployable in configurations that include point to multipoint (PMP), asshown in FIG. 3, as well as point to point (PTP). In other words, eachIBR 300 may communicate with one or more than one other IBR 300.

For 3G and especially for 4^(th) Generation (4G), cellular networkinfrastructure is more commonly deployed using “microcells” or“picocells.” In this cellular network infrastructure, compact basestations (eNodeBs) 316 are situated outdoors at street level. When sucheNodeBs 316 are unable to connect locally to optical fiber or a copperwireline of sufficient data bandwidth, then a wireless connection to afiber “point of presence” (POP) requires obstructed LOS capabilities, asdescribed herein.

For example, as shown in FIG. 3, the IBRs 300 include an Aggregation EndIBR (AE-IBR) and Remote End IBRs (RE-IBRs). The eNodeB 316 of the AE-IBRis typically connected locally to the core network via a fiber POP 320.The RE-IBRs and their associated eNodeBs 316 are typically not connectedto the core network via a wireline connection; instead, the RE-IBRs arewirelessly connected to the core network via the AE-IBR. As shown inFIG. 3, the wireless connection between the IBRs include obstructions(i.e., there may be an obstructed LOS connection between the RE-IBRs andthe AE-IBR).

FIG. 4 illustrates an exemplary deployment of an intelligent backhaulsystem (IBS) 400. The IBS 400 includes multiple IBRs 404 that canoperate in both obstructed and unobstructed LOS propagation conditions.The IBS 400 has several features that are not typical for conventionalline of sight microwave backhaul systems.

First, the IBS 400 includes multiple IBRs 404. Exemplary IBRs are shownand described below with reference to, for example, FIG. 5 of thepresent application, and are disclosed in detail in co-pending U.S.patent application Ser. No. 13/212,036, entitled Intelligent BackhaulRadio, filed Aug. 17, 2011, and FIG. 4 of co-pending U.S. patentapplication Ser. No. 13/271,051, entitled Intelligent Backhaul System,filed Oct. 11, 2011, the entireties of which is hereby incorporated byreference. It will be appreciated that there are many possibleembodiments for the IBRs as described herein and in co-pending U.S.patent applications Ser. No. 13/212,036 and Ser. No. 13/271,051. TheIBRs 404 are able to function in both obstructed and unobstructed LOSpropagation conditions.

Second, the IBS 400, optionally, includes one or more “IntelligentBackhaul Controllers” (IBCs) 408. As shown in FIG. 4, for example, theIBCs 408 are deployed between the IBRs 404 and other network elements,such as remote data access networks (ANs) 412 and a private core network(PCN) 416.

Third, the IBS 400 includes an “Intelligent Backhaul Management System”(IBMS) 420. As shown in FIG. 4, the IBMS 420 includes a private server424 and/or a public server 428. The IBMS 420 may also include an IBMSagent in one or more of the IBRs 404. The IBMS agent is described indetail with reference to FIG. 5 of the present application, FIG. 5 ofand copending U.S. application Ser. No. 13/271,051 and FIG. 7 ofcopending U.S. application Ser. No. 13/212,036. An IBMS agent may,optionally, be included within one or more of the IBCs 408.

FIG. 5 is a simplified block diagram of the IBRs 404 shown in FIG. 4. InFIG. 5, the IBRs 404 include interfaces 504, interface bridge 508, MAC512, a physical layer 516, antenna array 548 (includes multiple antennas552), a Radio Link Controller (RLC) 556 and a Radio Resource Controller(RRC) 560. The IBR may optionally include an IBMS agent 572. FIG. 5illustrates, in particular, an exemplary embodiment for powering the IBR404. In FIG. 5, the IBR 404 also includes a Power Supply 576 and anoptional Battery Backup 580. The Power Supply 576 may receive a PowerInput 584 or an alternative power input derived from a network interface504. It will be appreciated that the components and elements of the IBRsmay vary from that illustrated in FIG. 5.

In some embodiments, the IBR Interface Bridge 508 physically interfacesto standards-based wired data networking interfaces 504 as Ethernet 1through Ethernet P. “P” represents a number of separate Ethernetinterfaces over twisted-pair, coax or optical fiber. The IBR InterfaceBridge 508 can multiplex and buffer the P Ethernet interfaces 504 withthe IBR MAC 512. The IBR Interface Bridge 508 may also include anoptional IEEE 802.11 (or WiFi) adapter. IBR Interface Bridge 508 alsopreserves “Quality of Service” (QoS) or “Class of Service” (CoS)prioritization as indicated, for example, in IEEE 802.1q 3-bit PriorityCode Point (PCP) fields within the Ethernet frame headers, such thateither the IBR MAC 512 schedules such frames for transmission accordingto policies configured within the IBR of FIG. 5 or communicated via theIBMS Agent 572, or the IBR interface bridge 508 schedules the transferof such frames to the IBR MAC 512 such that the same net effect occurs.In other embodiments, the IBR interface bridge 508 also forwards andprioritizes the delivery of frames to or from another IBR over aninstant radio link based on Multiprotocol Label Switching (MPLS) orMultiprotocol Label Switching Transport Profile (MPLS-TP).

In general, the IBR utilizes multiple antennas and transmit and/orreceive chains which can be utilized advantageously by severalwell-known baseband signal processing techniques that exploit multipathbroadband channel propagation. Such techniques include Multiple-Input,Multiple-Output (MIMO), MIMO Spatial Multiplexing (MIMO-SM), beamforming (BF), maximal ratio combining (MRC), and Space Division MultipleAccess (SDMA).

The Intelligent Backhaul Management System (IBMS) Agent 572 is anoptional element of the IBR that optimizes performance of the instantlinks at the IBR as well as potentially other IBR links in the nearbygeographic proximity including potential future links for IBRs yet to bedeployed.

FIG. 6 illustrates an exemplary detailed embodiment of the IBR 400illustrating some additional details. FIG. 6 corresponds to FIG. 7 ofcopending U.S. application Ser. No. 13/212,036 and FIG. 6 of copendingU.S. application Ser. No. 13/271,051. As shown in FIG. 6, the IBR 400includes interfaces 604, interface bridge 608, media access controller(MAC) 612, modem 624, which includes one or more demodulator cores andmodulator cores, channel multiplexer (MUX) 628, RF 632, which includestransmit chains (T×1 . . . T×M) 636 and receive chains (R×1 . . . R×N)640, antenna array 648 (includes multiple directive gainantennas/antenna elements 652), a Radio Link Controller (RLC) 656, aRadio Resource Controller (RRC) 660 and the IBMS agent 572. It will beappreciated that the components and elements of the IBRs may vary fromthat illustrated in FIG. 6.

The primary responsibility of the RRC 660 is to set or cause to be setat least the one or more active RF carrier frequencies, the one or moreactive channel bandwidths, the choice of transmit and receive channelequalization and multiplexing strategies, the configuration andassignment of one or more modulated streams amongst the one or moremodulator cores, the number of active transmit and receive RF chains,and the selection of certain antenna elements and their mappings to thevarious RF chains. Optionally, the RRC 660 may also set or cause to beset the superframe timing, the cyclic prefix length, and/or the criteriaby which blocks of Training Pilots are inserted. The RRC 660 allocatesportions of the IBR operational resources, including time multiplexingof currently selected resources, to the task of testing certain linksbetween an AE-IBR and one or more RE-IBRs. The MAC 612 exchanges data toand from a remote access data network via coupling to at least theinterface bridge 608 and to and from at least one other intelligentbackhaul radio. The MAC 612 inputs receive data from a receive path andoutputs transmit data to the transmit path.

Additional details regarding the features and operation of the IBR 400are disclosed in copending U.S. application Ser. Nos. 13/212,036 and13/271,051, the entireties of which are hereby incorporated byreference. For example, the various policies and configurationparameters used by the RRC 660 to allocate resources within and amongstIBRs with active links to each other are sent from the IBMS Agent 572 tothe RRC 660. In the return direction, the RRC 660 reports operationalstatistics and parameters back to the IBMS Agent 572 both from normaloperation modes and from “probe in space” modes as directed by the IBMSAgent 572.

With reference back to FIG. 5, the IBR 400 also includes a power supply576. In some embodiments, a Power Input 584 to the Power Supply 576 isan alternating current (AC) supply of, for example, 120V, 60 Hz or 240V,50 Hz or 480V, 60 Hz, 3-phase. Alternatively, the Power Input 584 may bea direct current (DC) supply of, for example, +24V, −48V, or −54V.

The Power Supply 576 outputs voltage to other elements of the IBR 404.In some embodiments, typical Power Supply 576 output voltages are DCvoltages such as +12V, +5V, +3.3V, +1.8V, +1.2V, +1.0V or −1.5V.

In the event that the Power Supply 576 loses its Power Input 584 for anyreason, the Battery Backup 580 may provide an alternative power input tothe Power Supply 576 so that IBR operation may continue for some periodof time. This is particularly advantageous for ANs at remote locationswherein critical communications services may be needed during temporarymain power supply outages. The Battery Backup 580 is typically chargedby a DC input such as +18V or +12V from the Power Supply 576.

As shown in FIG. 5, the Power Supply 576 may optionally receive a powerinput derived from a network interface 504. For IBRs that requireapproximately 15 W of power or less, an exemplary power input from anetwork interface 504 is “Power over Ethernet” (or PoE) as defined byIEEE 802.af. For other IBRs that require approximately 25 W of power orless, an exemplary power input from a network interface 504 is “Powerover Ethernet Plus” (or PoE+) as defined by IEEE 802.at. Typical DCvoltages associated with POE are +48V or −48V, and typical DC voltagesassociated with PoE+ are +54V or −54V.

In some embodiments, it may be desirable for the Power Supply 576 tooperate from AC main supplies, such as 120V, 240V or 480V, in twoseparate structures. First, an AC to DC converter creates a DC powerinput such as +24V, +12V, +18V, −48V, −54V, etc; and, second, a DC to DCconverter creates the DC voltages required internal to the IBR such as+12V, +5V, +3.3V, +1.8V, +1.2V, +1.0V, −1.5V, etc.

In embodiments in which the Power Supply 576 includes these two separatestructures, the AC to DC converter portion of the Power Supply 576 maybe physically external to the main enclosure of the IBR while the DC toDC converter portion of the Power Supply 576 is internal to the mainenclosure of the IBR. Similarly, in some embodiments, the Battery Backup580 may be external to the main enclosure of the IBR. Similarly, forIBRs with a WiFi Adapter capability as described in copending U.S.application Ser. No. 13/212,036, the WiFi Adapter may be positionedinternal to or external of the enclosure of the IBR.

The IBMS Agent shown in FIG. 5 can function as described in copendingU.S. application Ser. No. 13/212,036, copending U.S. application Ser.No. 13/271,051 and/or as described in more detail below. As shown inFIG. 5, in some embodiments, the Power Supply 576 may provide a controlsignal (Power Status) 592 to the IBMS Agent 572 that communicates, forexample, if the Power Supply 576 is operating from a Power Input 584, aderived power input from a network interface 588, or from an optionalBattery Backup 580 and possibly an estimated current reserve level forsuch Battery Backup. In such embodiments, the IBMS Agent 572 may relaythis status 592 to other elements of the IBS 400.

FIG. 7 illustrates a simplified block diagram of IBCs 408A-C of FIG. 4.As shown in FIG. 7, the IBC 408 includes a plurality of physical layerports 704 that include a plurality of network interfaces 708. The IBC408 also includes a wireless adapter 712, an IBC managed switch 716, aremote power switch 720, an IBMS agent 724, and an IBC host controller728. The IBC 408 may also include a power supply 732 and an optionalbattery backup 736.

In some embodiments, the plurality of Network Interfaces 708 aretypically an Ethernet or IEEE 802.3 interfaces based on copper wires orfiber optics. Typically, such Ethernet interfaces support data rates of1 Gb/s, 10 Gb/s or higher. Each Network Interface 708 is typicallycoupled to a respective Physical Layer Port 704 and in turn typicallycoupled to a respective Layer 2 port within the IBC Managed Switch 716.

In some embodiments, the IBC Managed Switch 716 is a substantiallyconventional Layer 2 switch in accordance with standard features definedby various IEEE 802.1 and 802.2 specifications. For example, the IBCManaged Switch 716 may be compliant with IEEE 802.1D for MAC-layerbridging across various ports and IEEE 802.1Q for adding Virtual LocalArea Networking (VLAN) tags and the 3-bit 802.1p Priority Code Point(PCP) field. VLAN capability enables the IBC Managed Switch 716 to besegmented amongst certain subsets of the available switch ports and thePCP fields enable certain frames to have higher delivery priority thanother frames. Other exemplary IBC Managed Switch 716 capabilitiesinclude compliance with IEEE 802.1X for access control, IEEE 802.1AB forlink layer discovery, IEEE 802.1AE for MAC layer security, and IEEE802.1AX for link aggregation and resiliency as well as numerousderivative standards specifications based on the above list (and IEEE802.1D and 802.1Q).

In some embodiments, the IBC Managed Switch 716 may also have certainrouting or packet-forwarding capabilities, such as routing by InternetProtocol (IP) address or packet-forwarding by Multiprotocol LabelSwitching (MPLS) in a substantially conventional fashion. In particular,some IBC Managed Switches 716 may operate as an MPLS Label Switch Router(LSR) while other MPLS-compatible devices within certain ANs operate asLabel Edge Routers (LERs that represent ingress and egress points forpackets within an MPLS network). In other embodiments, the IBC ManagedSwitch 716 may alternatively or additionally operate as an LER thataffixes or removes MPLS labels having at least a label value oridentifier, a 3-bit traffic class field (analogous to the PCP filed inIEEE 802.1 or the precedence bits in the Type of Service field in IPheaders), and a time-to live field. Based on MPLS labels, such IBCManaged Switches 716 forward packets to particular ports (or possiblysets of ports in a VLAN segment) corresponding to certain ANs or IBRs asassociated with particular “tunnels” to other MPLS LERs or LSRs, orbased on MPLS ingress or egress ports from the IBC Managed Switch 716when operating as an MPLS LER.

In some embodiments, the IBC Managed Switch 716 may alternatively oradditionally operate as an MPLS Transport Profile (MPLS-TP) switch toprovide connection-oriented, packet-switching on specific paths betweensuch an IBC and typically another such IBC or peer MPLS-TP device at theedge of the PCN 416.

In some embodiments, the IBC Managed Switch 716 may alternatively oradditionally operate as a Carrier Ethernet switch that provides one ormore Ethernet Virtual Connections (EVCs) according to standardspromulgated by the Metro Ethernet Forum (MEF). For example, in suchembodiments, certain IBC Network Interface 708 ports may be configuredwithin the IBC Managed Switch 716 as an MEF User Network Interface (UNI)port. Typically, such an IBC UNI port, if associated with an AN 412 atan IBC 408 on a remote location, can then be paired to another UNI(possibly at another IBC) at the edge of the PCN (at an aggregationpoint) via an EVC. Depending on the configuration of the IBC ManagedSwitch 716 and other network elements, the EVC could be an E-Line suchas an Ethernet Private Line, an E-LAN such as an Ethernet Private LAN,or an E-Tree. For deployments such as shown in FIG. 4, an exemplary IBC408 with MEF capability can also interact with one or more IBR-basedlinks to provide Committed Information Rate (CIR) and Excess InformationRate (EIR). These interactions may be direct via one or more NetworkInterfaces 708 or optionally indirect via the IBMS 420.

As shown in FIG. 7, the IBC 408 may also include an IBC Host Controller728. The IBC host controller 728 may be implemented as software on oneor more microprocessors. In some embodiments, the IBC Host Controller728 directs the operation of the IBC Managed Switch 716 according topolicies provided to the IBC 408. The scope of policies applicable to agiven IBC 408 depends on the particular set of IBC Managed Switchcapabilities, as described above. Typical policies relate to the mappingbetween Network Interface 708 ports assigned to ANs 412 and thoseassigned to IBRs 404 as realized within the IBC Managed Switch 716. Inmany cases, the policies may be derived from Service Level Agreements(SLAs) that govern the desired and/or required performance attributes ofbackhaul connections between particular ANs 412 or users of ANs 412 andthe PCN 416.

In some embodiments, the policies administered by the IBC HostController 728 in directing the behavior of the IBC Managed Switch 716are supplied by the IBMS Agent 724. In some embodiments, such policiesare alternatively or additionally supplied by a console interface to theIBC 408 at the time of initial deployment or later.

As shown in FIG. 7, the IBC 408 may also include an IEEE 802.11 WirelessLAN interface (i.e. a “WiFi Adapter”) 712. In some embodiments, the WiFiAdapter 712 may be configured as a public or private IEEE 802.11 accesspoint based on one or more standard specifications such as IEEE 802.11g,IEEE 802.11n or subsequent IEEE 802.11 variants. In this situation, theIBC effectively integrates a WiFi-based AN within the IBC that isattached to an internal port of the IBC Managed Switch 716 such thattraffic to or from the WiFi AN can be bridged to one or more IBRs 404,or passed to an IBMS Agent 724, 576 (at either the IBC 408 or within theone or more attached IBRs 404) or the IBC Host Controller 728 overstandard network protocols, such as TCP or UDP on IP. This permitsterminal devices such as smartphones, tablets or laptop computers to actas a console input to easily access, monitor or configure policies andperformance data associated with the IBC 408, or via the IBC ManagedSwitch 716, also access, monitor or configure policies and performancedata at one or more IBRs 404 attached to the IBC 408. This isparticularly advantageous for IBCs 408 and/or IBRs 404 that are mountedin locations without easy physical accessibility, such as those mountedon street lamps, utility poles, and building sides or masts that areinsufficient to support humans at the IBC or IBR mounting height.Similarly, such access to the IBC 408 and attached IBRs 404 can berealized via a WiFi Adapter within one of the attached IBRs 404 bybridging across an exemplary IBC 408.

Alternatively, in some embodiments, the WiFi Adapter 712 may beoptionally connected to the IBC Host Controller 728 (instead of the IBCManaged Switch 716) over a serial bus or other internal bus suitable forperipheral I/O devices. In this embodiment, the WiFi Adapter 712 wouldnot be suitable for public or private WiFi access point usage atcommercially-desirable throughputs, but may still be suitable forconsole mode operation to access, monitor or configure policies andperformance data at the IBC 408 and possibly at attached IBRs 404 to theextent permitted by the software executing on the IBC Host Controller728.

In some embodiments, the optional WiFi Adapter 712 may be physicallycontained within the enclosure of the IBC 408, subject to considerationof antenna location for effective propagation especially for elevatedmounting and ground level access. In other embodiments, the optionalWiFi Adapter 712 may be external to the IBC physical enclosure andeither connected via an external Network Interface 708 or via anexternal mounting interface to the IBC Managed Switch 716 optimizedspecifically for an attached external WiFi Adapter.

For embodiments of the IBC 408 or IBR 404 that include a WiFi Adapter,it is possible to access such devices with the WiFi Adapter configuredas an access point, as a peer to peer station device, as a stationdevice wherein the portable terminal (smartphone, tablet, laptopcomputer, etc.) is configured as an access point, or via WiFi direct.

In FIG. 7, the IBC 408 also includes a Power Supply 732 and an optionalBattery Backup 736. The Power Input 740 to the Power Supply 732 may bean alternating current (AC) supply of, for example, 120V, 60 Hz or 240V,50 Hz or 480V, 60 Hz, 3-phase. Alternatively, the Power Input 740 may bea direct current (DC) supply of, for example, +24V, −48V, or −54V.Typical Power Supply 732 output voltages to the various elements of theIBC are DC voltages such as +12V, +5V, +3.3V, +1.8V, +1.2V, +1.0V or−1.5V.

The optional Battery Backup 736 may be charged by a DC input, such as+18V or +12V, from the Power Supply 732. In the event that the PowerSupply 732 loses its Power Input 740 for any reason, the Battery Backup736 may provide an alternative power input to the Power Supply 732 sothat IBC operation may continue for some period of time. This isparticularly advantageous for ANs at remote locations wherein criticalcommunications services may be needed during temporary main power supplyoutages.

In some embodiments, a Power Supply 732 that operates from AC mainsupplies, such as 120V, 240V or 480V, includes two separate structures.First, the Power Supply 732 includes an AC to DC converter that createsa DC power input such as +24V, +12V, +18V, −48V, −54V, etc.; and,second, the Power Supply 732 includes a DC to DC converter that createsthe DC voltages required internal to the IBC such as +12V, +5V, +3.3V,+1.8V, +1.2V, +1.0V, −1.5V, etc.

In these embodiments where the Power Supply 732 includes two separatestructures, the AC to DC converter portion of the Power Supply 732 maybe physically external to the main enclosure of the IBC 408 while the DCto DC converter portion of the Power Supply 732 remains internal to themain enclosure of the IBC 408. Similarly, for certain IBC embodiments,the Battery Backup 736 may be external to the main enclosure of the IBC408.

Note that unlike the IBR 404, the IBCs 408 typically are not configuredto use standards-based PoE or PoE+ as an alternate power input forpowering the IBC 408. Instead, the IBCs 408 combine a PoE or PoE+ powerinjection capability that can be switched to some or all of the NetworkInterfaces 708 from a Remote Power Switch 720 via the Physical LayerPorts 704. Typically the Network Interface Power Input 744, such as +48Vor −48V for PoE or +54V or −54V for PoE+, is provided by the PowerSupply 732 and then switched under the direction of the IBC HostController 728 at the Remote Power Switch 720. The specific NetworkInterface 408 ports receiving PoE or PoE+ power from the Remote PowerSwitch 720 are determined based on configuration parameters set at timeof deployment by, for example, console mode input or the IBMS Agent 724or updated from time to time via the IBMS Agent 724.

Note also that as for the IBR 404, exemplary IBCs 408 may also have thePower Supply 732 provide a control signal (Power Status) 748 to at leastthe IBMS Agent 724 or the IBC Host Controller 728 that communicates, forexample, if the Power Supply 732 is operating from a Power Input 740 orfrom an optional Battery Backup 736 and possibly an estimate currentreserve level for such Battery Backup 736. As with the IBR 404, suchPower Status 748 may be relayed by the IBMS Agent 724 to other IBMSelements. Alternatively or additionally, the IBMS Agent 724 and/or IBCHost Controller 728 may choose to restrict or terminate PoE or PoE+power to certain Network Interfaces 708, whether AN 412 or IBR 404,based on policies as may currently be set at the IBC 408. Suchrestrictions or terminations may also consider the actual powerconsumption of particular Network Interfaces 708 as may be determined bythe Remote Power Switch 720 and reported to the IBC Host Controller 728.One example of when it is advantageous to terminate PoE or PoE+ powerunder backup conditions is when the device, powered by the IBC 408, suchas an AN 412 or IBR 404, are known to the IBC 408 (possibly via theIBMS) to have their own back-up power sources.

In some embodiments, the IBCs 408 may also provide synchronizationcapabilities to ANs 412, IBRs 404 or other network devices attached tothe Network Interfaces 708. One methodology for providingsynchronization at remote locations such as IBCs 408A or 408C in FIG. 4is to attach or embed a Global Positioning Satellite (GPS) receiver inan IBC (not shown in FIG. 7) and then distribute a one pulse per second(1 PPS) output to applicable ANs 412 and IBRs 404. However, the GPS maynot operate effectively in the street level obstructed propagationconditions. An alternative approach to establishing synchronization atthe IBC 408 for distribution to ANs 412 or IBRs 404 is to extend asynchronization methodology already in use in the PCN 416.

In some embodiments, the synchronization methodology of the IBCs 408 isSynchronous Ethernet (SyncE). With SyncE, the Network Interface clockfrequency of a designated physical port can be precisely applied by theIBCs 408 to any other designated Network Interface physical port.Typically, this is performed by conventional circuitry comprised withinthe Physical Layer Ports 704 of the IBC 408. With SyncE, the IBC 408 canensure that the Network Interface clock frequencies at certain physicalports are all identical over time to a master clock frequency typicallysupplied from within the PCN 416. This is particularly advantageous fornetwork deployments where synchronous applications such as voice orvideo communications are desired to traverse multiple backhaul links asillustrated, for example, in FIG. 4.

In other embodiments, the synchronization methodology is IEEE 1588v2 orsubsequent variations thereof. With IEEE 1588v2, the IBC 408 examinestimestamps within certain packets (or frames) to either derive precisetiming for internal or local distribution purposes or to modify suchtimestamps to account for delays traversing the IBC 408 or other networklinks or elements. Typically, this is performed by conventionalcircuitry comprised within the IBC Managed Switch 716 and/or PhysicalLayer Ports 704.

IBRs 404 can also include circuitry for SyncE or IEEE 1588v2synchronization methodologies. In the SyncE case, the IBC 408 can onlypass SyncE clock frequency synchronization from a master clock in thePCN 416 to remote ANs 412 over IBR links to the extent that the IBRs 404include SyncE capability. In the IEEE 1588v2 case, the IBRs 404 operateacross an instant AE-IBR to RE-IBR link as an IEEE 1588v2 transparentclock wherein the time stamp at ingress to such a link (for example, atIBR 404F in FIG. 4) is modified at egress from the link (for example, atIBR 404E in FIG. 4) to account for the actual latency incurred intraversing the link.

Similarly, in some embodiments, the IBC 408 operates as an IEEE 1588v2transparent clock that modifies timestamps to account for actual latencyincurred as a packet traverses from one IBC Network Interface physicalport to another. In other embodiments, the IBC 408 alternatively oradditionally operates as an IEEE 1588v2 boundary clock that has theability to determine latency between such an IBC and another IEEE 1588v2boundary clock or transparent clock device within the network based ondelays determined between such devices.

In some embodiments, the IBCs 408 also have the capability to operate asan IEEE 1588v2 master or grandmaster clock as may be directed by theIBMS Agent 724 based on policies or messages passed from an IBMS PrivateServer 424 or IBMS Global Server 428 as shown in FIG. 4.

As shown in FIG. 7, the IBC 408 includes an IBMS Agent 724. The IBMSagent 724 may be similar to the IBR IBMS Agent 572 shown in anddescribed with respect to FIG. 5 of the present application andcopending U.S. patent application Ser. No. 13/271,051, and shown in anddescribed with respect to FIG. 7 of copending U.S. patent applicationSer. No. 13/212,036. The IBMS Agent 724 can be used to set numerousexemplary operational policies or parameters such as, for example,access control, security key management, traffic shaping orprioritization, load balancing, VLAN segmentation, routing paths, portmirroring, port redundancy, failover procedures, synchronizationmethodologies and port mappings, power management modes, etc. The IBMSAgent 724 can also be used to report numerous operational parameters orstatistics to the IBMS Private Server 424 or IBMS Global Server 428,such as, for example, active sessions, connected device identifiers, MACaddresses, packet counts associated with particular MAC addresses orphysical ports, packet or frame error rates, transfer rates, latencies,link availability status for certain ports, power consumption forcertain ports, power status of the IBC, etc.

In embodiments where a CBR may be utilized for a particular link (notshown in FIG. 4), the IBMS Agent 724 within the IBC 408 can also act asa proxy IBMS Agent for the CBR to the extent the IBC 408 can determinecertain operational parameters or statistics or set certain operationalparameters or policies for such CBR. Optionally, the IBC 408 may alsoadditionally or alternatively determine or set certain operationalparameters or policies for a CBR or a switch port connected to such CBRbased on OpenFlow (http://www.openflow.org/), Simple Network ManagementProfile (SNMP) or other industry standard network element managementprotocols.

With reference back to FIG. 4, the IBS 400 includes at least one IBMSServer 424, 428 which communicates with IBMS Agents 572, 724 within IBRs404 and IBCs 408. In many deployments, operators of a PCN 416 may preferto maintain an IBMS Private Server 424 within the PCN 416. Such an IBMSPrivate Server 424 typically serves as a secure and private point ofdatabase storage and policy management for all IBMS Agents 572, 724within a particular PCN 416. Typically, such an IBMS Private Server 424is implemented in a mirrored configuration of two or more substantiallyconventional servers and databases for both load balancing andredundancy purposes. In some embodiments, the IBMS Private Server 424 isimplemented external to the PCN 416, for example as a virtual server anddatabase within the IBMS Global Server 428, but still maintained as asecure and private point within the PCN 416 via a virtual privatenetwork (VPN) connection or equivalent technique.

One exemplary capability of the IBMS Private Server 424 includesstoring, archiving and indexing data and statistics received from IBMSAgents in IBCs 408 and IBRs 404 associated with a particular PCN 416. Anadditional exemplary capability of the IBMS Private Server 424 includesgeneration and/or modification of policies used to configure, manage,optimize or direct, via IBMS Agents, the operation of IBCs 408 and IBRs404 associated with a particular PCN 416. The IBMS Private Server 424may also access information from or export information to a PrivateDatabase 440.

In some embodiments of the IBMS Private Server 424, certain raw orstatistical data related to, for example, IBR operational parameters,are provided to the IBMS Global Server 428. Exemplary IBR operationalparameters include channel frequency, modulation and coding scheme (MCS)index, transmit power control (TPC) value, signal to noise ratio (SNR)or signal to noise and interference ratio (SINR), superframe timingparameters, observed interferers, location, antenna configurations,antenna orientations, etc. The IBMS Private Server 424 may also receivepolicy recommendations for IBRs 404 and IBCs 408 associated with aparticular PCN 416 from the IBMS Global Server 428. Such data and/orstatistical summaries thereof may be maintained in an IBMS PrivateDatabase 432 associated with a particular IBMS Private Server 424.

As shown in FIG. 4, the IBS 400 may also include an IBMS Global Server428 coupled to the public Internet 444. For IBRs 404 and IBCs 408deployed in PCNs 416 where an IBMS Private Server 424 is not used, theIBMS Global Server 428 and such IBRs 404 and IBCs 408 can be configuredsuch that the IBMS Global Server 428 provides the capabilities describedabove for the IBMS Private Server 424 for such IBRs 404 and IBCs 408.

The IBMS Global Server 428 communicates with IBRs 404 and IBCs 408 andIBMS Private Servers 424 such that the IBMS Global Server 428 has accessto operational parameters for all IBRs 404 and IBCs 408 across all PCNs416 capable of interacting with each other, either in network trafficflow or via common access to wireless propagation space.

As also shown in FIG. 4, the IBMS Global Server 428 maintains dataassociated with the operational parameters of the IBRs 404 (and possiblyalso IBCs 408) within an IBS 400 in an IBMS Global Database 436. TheIBMS Global Server 428 is typically implemented in a mirroredconfiguration of two or more substantially conventional servers anddatabases for both load balancing and redundancy purposes. In someembodiments, the IBMS Global Server 428 may be virtualized within acloud computing cluster that provides on demand server computingresources in response to instantaneous loading of the IBMS Global Server428.

As shown in FIG. 4, the IBMS Global Server 428 preferably accesses oneor more Public Databases 452 over, for example, the public Internet 444.In certain embodiments, the IBMS Global Server 428 accesses data orinformation in such Public Databases 452 in determining recommendedpolicies for IBRs 404 or IBCs 408 within the IBS 400. In otherembodiments, the IBMS Global Server 428 either additionally oralternatively provides data or information to such Public Databases 452to, for example, enable other radio spectrum users to develop policiesin view of deployed IBRs 404 or comply with applicable regulatoryrequirements. One example of a Public Database 452 is informationavailable within the website of the United States Federal CommunicationsCommission (FCC) at www.fcc.gov for certain fixed service radiolocations, antenna orientations, antenna characteristics, transportpowers and channel frequencies. Another example of the Public Database452 is a listing of locations and parameters associated with certain ANs412, such as WiFi access points. Other examples of Public Databases 452include Geographic Information Services (GIS) databases of topography,landscape, and building locations and descriptions as may be maintainedby various government agencies serving the geographic region encompassedby an exemplary IBS 400.

As also shown in FIG. 4, the IBMS Global Server 428 has the capabilityto access data or information from or provide data or information tocertain Proprietary Databases 448 over the public Internet 444 to theextent that the operator of the IBMS Global Server 428 procures accessprivileges to such Proprietary Databases 448. Exemplary ProprietaryDatabases 448 may provide spectrum usage information or detailed GISdata for the geographic region encompassed by an exemplary IBS 400.Alternatively, such Proprietary Databases 448 may be vehicles tomonetize data or information provided to such databases by the IBMSGlobal Server 428.

In certain embodiments where the IBMS Global Server 428 provides data orinformation to one or more Public Databases 452 or Proprietary Databases448, some or all these databases may be within the IBMS Global Database436 of FIG. 4.

The IBMS Global Server 428 of FIG. 4 may also have an analyticalcapability to determine estimated radio channel propagation effects fordeployed or proposed IBR links in view of the other IBR links and otherspectrum users within the geographic region encompassed by an exemplaryIBS 400. As shown in FIG. 4, an exemplary IBMS Global Server 428 canaccess either locally or over the public Internet Cloud ComputingResources 456 to execute algorithms associated with such analyticalcapability, as described in further detail hereinafter. In general,radio channel propagation effects are simulated with such algorithms inview of, for example, radio locations (including antenna height),antenna characteristics and orientations, radio characteristics, channelfrequencies and bandwidths, transmit powers, and GIS data describing thepropagation environment.

In addition, the IBMS Private Server 424 or IBMS Global Server 428 mayalso provide traditional FCAPS information. This FCAPS information canbe accessed in certain embodiments by the PCN operator by a client incommunication with the IBMS Private Server 424 or IBMS Global Server428. Alternatively or additionally, in other embodiments, such FCAPSinformation may be exported by the IBMS Private Server 424 or IBMSGlobal Server 428 to another Network Management System (NMS) aspreferred by a particular PCN operator.

In some embodiments, the IBMS Private Server 424 or IBMS Global Service428 also provides users, such as a particular PCN operator, with thecapability to determine additional IBS Components for network changes,moves, adds, or redundancies. This may also be provided via a clientinterface or via export to another NMS. Typically, the IBMS PrivateServer 424 or IBMS Global Server 428 considers the particular goal ofthe IBC network modification, such as for example only, changing theamount of backhaul capacity at a remote location, moving a remote AN412/IBR 404 to a different location, adding another remote location withone or more ANs, or providing an additional redundancy mechanism at aremote location. In view of the capabilities of the IBMS 420 asdescribed above, then with knowledge of available IBR and IBC productvariants or upgrade capabilities, the IBMS Private Server 424 or IBMSGlobal Server 428, acting as an expert system in exemplary embodiments,then recommends particular additional IBR or IBC equipment or upgradesto realize the requested goal.

In some embodiments, the IBMS Private Server 424 or IBMS Global Server428 also actively monitors the IBS 400 with the IBMS capabilitiesdescribed above such that, acting as an expert system in exemplaryembodiments, it provides unsolicited recommendations for additional IBRor IBC equipment or upgrades or modified configuration parameters forexisting deployed IBRs, IBCs and certain supported CBRs. Typically, forexisting deployed IBRs or IBCs that are in communication with the IBMSPrivate Server 424 or IBMS Global Server 428, such modifiedconfiguration parameters associated with either preferential operationor a software-only equipment upgrade can be transferred to theparticular IBRs or IBCs over network connections to avoid a need formanual configuration and/or travel by an operator to the remotelocation. Optionally, such an IBMS Server 424, 428 may also link to acommerce server or application to invoice as appropriate for suchupgrades.

In some embodiments, the IBMS Private Server 424 or IBMS Global Server428 generates a configuration file or list of configuration settings forany additional IBRs or IBCs or upgraded IBRs or IBCs in view of theoverall IBS network deployment and IBMS capabilities described above. Insome exemplary embodiments, such a configuration file or list issupplied via email or network connection to an installer of the IBR orIBC for initial deployment provisioning using a console mode terminaleither wireline connected to the instant IBR or IBC or wirelessly (i.e.WiFi) connected to the IBR or IBC. Alternatively or additionally, otherexemplary embodiments allow network discovery between the instant IBR orIBC being provisioned upon deployment and the IBMS Private Server 424 orIBMS Global Server 428 such that the initial provisioning configurationcan be transferred to the IBR or IBC without manual configuration.

Although FIGS. 3-7 and the descriptions thereof herein depict the IBC408 as a separate network element from that of the IBR 404, this is notan absolute requirement for all embodiments of an IBS 400. In someexemplary embodiments, it may be advantageous to integrate some or allof the IBC functionality described herein within a single physicalentity of the IBR 404. Alternatively, in other exemplary embodiments, itmay be advantageous to utilize separate physical enclosures respectivelyfor the IBR 404 and IBC 408 such that an IBC physical entity candirectly attach to an IBR physical entity without separate mounting orcables. Such IBC/IBR combinations may maintain multiple physical networkinterface ports for connection to one or more ANs and one or moreadditional IBRs without combined or attached IBC.

In some IBS deployment scenarios, CBR links may be used in addition toor alternatively to the IBR links shown in FIG. 4. For such situations,certain IBC deployments may serve as a proxy between such a CBR and theIBMS Private Server 424 or IBMS Global Server 428 such that the IBMSAgent in such IBC 408 provides operational parameters for the CBR linkregarding throughput or congestion. This optional capability providesadditional information to the IBMS Private Server 424 or IBMS GlobalServer 428 on which to base its recommendations for configurations ofIBRs 400 and IBCs 408 within the IBS 400 or to modify policies at suchIBRs 404 and IBCs 408. Alternatively, the IBMS Private Server 424 orIBMS Global Server 428 may determine such information and set suchoperational parameters for either CBRs or other network elementsincluding routers and switches via OpenFlow or other such industrystandard network management protocols.

In exemplary IBCs 408, network traffic shaping and classifying is basedon policies that may be updated by the IBMS Private Server 424 or IBMSGlobal Server 428 via the IBMS Agent at the IBC 408 as described above.This is advantageous to the PCN operator because such policies canreflect or enforce provisions of Service Level Agreements (SLAs) forbackhaul between certain ANs and elements within the PCN. For example,an SLA may require minimum throughput at all times to or from certainANs with simultaneous maximum latencies for such traffic for certaintraffic types. The IBMS Private Server 424 or IBMS Global Server 428 cantranslate such SLA requirements to policies that can be set at a givenIBC 408 or IBR 404. To the extent that traffic contention occurs at anIBC 408 due to finite switching bandwidth or IBR backhaul capacity, theIBMS Agent may further set policies on the order in which one or moreSLA requirements is violated. Similarly, to the extent that spectrumresource contentions in a local geographic area amongst the IBR (or CBR)links under IBMS Private Server 424 or IBMS Global Server 428 managementcauses one or more SLA requirements to be violated, the order in whichtraffic is controlled or spectrum access restricted may be set viapolicies communicated to the IBMS Agents 572, 624 of affected IBCs 408or IBRs 404. In the above examples, the IBMS Private Server 424 or IBMSGlobal Server 428 may also set such policies in view of minimizingfinancial penalties to the PCN operator in situations where SLArequirements are violated.

In exemplary embodiments, the IBS 400 provides redundant backhaul pathsfrom certain ANs 412 to elements within the PCN 416 as depicted, forexample, at IBC 408A in FIG. 4. In one example, as shown in FIG. 4, IBC408A may direct traffic to or from the one or more ANs 412 via redundantIBRs 404 as shown. The instantaneous switching of AN traffic to the twoor more IBRs 404 in a redundancy configuration can be set by policies atthe IBC 408. The policies can be updated via the IBMS Agent at the IBC408 in communication with the IBMS Private Server 424 or IBMS GlobalServer 428. Such policies can include designation of redundancy orderamongst multiple IBRs 404 connected to a particular IBC 408 in case anIBC port condition indicates an IBR equipment or link failure or linkconditions degraded past a threshold and load balancing parametersamongst available IBR links at an IBC 408. One load balancing strategythat may be deployed via policies at the IBC 408 in communication withIBMS elements is to uniformly distribute all classes of AN trafficamongst available IBRs 404. An alternate load balancing strategy in viewof overall IBS operation as determined via the IBMS Private Server 404or IBMS Global Server 428 and communicated policies to the IBMS Agent724 of the IBC 408 may be to direct no traffic or only certain classesof traffic to particular IBR links on particular IBC network interfaceports. Numerous other redundancy, load balancing, path routing and failover strategies are also possible.

In certain exemplary embodiments, an IBC 408 may also be directed viaIBMS elements to localize traffic amongst ANs 412 using, for example,MPLS. Alternatively, an IBC 408 may be directed to preferentially choosecertain MPLS paths or IP routes based on network congestion ascommunicated to its IBMS Agent based on determination of congestion ateither an IBMS Server or other network element from IBMS Agent messagesor other method such as Open Flow.

In some embodiments, the IBMS Private Server 424 or IBMS Global Server428 acts as an RF spectrum coordinator for an IBS 400 within a givengeographic region. For example, an exemplary IBMS Private Server 424 orIBMS Public Server 428 with the capabilities described herein maycommunicate policies or configuration parameters to some or all IBRs 404in an IBS 400 such that each IBR 404 is directed to use or instructed tofavor operation at particular channel frequency, channel bandwidth,antenna selection or overall radiation orientation, or within a maximumtransmit power level. Such policies or configuration parameters may bedetermined at exemplary embodiments of the IBMS Private Server 424 orIBMS Global Server 428 in view of measured data at various IBRs 404 asreported via respective IBMS Agents and alternatively or additionally inview of RF propagation modeling using available database and computingresources. For example, in the exemplary IBS 400 shown in FIG. 4, the RFlinks between IBRs 404D and 404B and IBRs 404A and 404C may contend forcommon RF spectrum resources. To the extent that the exemplary IBMSPrivate Server 424 or IBMS Global Server 428 determines that suchcontention is not sufficiently mitigated by the affected IBRs 404 undertheir current policies and configuration parameters in view of, forexample, measured data, interference cancellation capabilities, antennaselections, characteristics and orientations, simulated propagationeffects, traffic conditions, applicable SLAs, etc., then such exemplaryIBMS Private Server 424 or IBMS Global Server 428 may send updatedpolicies or configuration parameters to one or more affected IBRs 404via their IBMS Agents. In such an example, this may cause such IBRs 404to use or favor usage of a particular RF channel frequency or sub bandof frequencies, to use a different channel bandwidth, to avoid certainantenna selections or orientations, or to restrict operation to aspecified maximum transmit power level. In exemplary embodiments, theforegoing process may also consider interference from non IBR users ofthe same RF spectrum, such as CBRs, or interference to other users ofthe instant RF spectrum as may be required under certain spectrumregulations.

In some embodiments, the IBMS Private Server 424 or IBMS Global Server428 acts as a topology coordinator for an IBS 400 within a givengeographic region typically in conjunction with RF spectrum coordinatorcapability described above. For example, an exemplary IBMS PrivateServer 424 or IBMS Global Server 428 with the capabilities describedherein may communicate policies or configuration parameters to some orall IBRs 404 in an IBS 400 such that each IBR 404 is directed toassociate or instructed to favor association with certain otherdesignated IBRs 404. Such policies or configuration parameters may bedetermined at exemplary embodiments of the IBMS Private Server 424 orIBMS Global Server 428 in view of reported traffic flows at certain IBCnetwork interface ports or over certain IBR links, reported linkperformance metrics at certain IBRs, instant interference and RFspectrum coordination considerations, desired redundancy, failover orload balancing goals, and applicable SLA requirements including, forexample, localized network congestion or access cost considerations. Forexample, in the IBS 400 shown in FIG. 4, IBR 404A is shown as associatedwith IBR 404C, IBR 404D is shown as associated with IBR 404B, IBR 404Eis shown as associated with IBR 404F, and IBR 404K is shown asassociated with IBR 404G. However, based on reported measurement data orRF propagation modeling, the IBMS Private Server or IBMS Global Servermay also determine that IBRs 404A and 404D can alternatively associatewith IBR 404C or 404F, IBR 404E can alternatively associate with IBR404C or 404G, and IBR 404K can alternatively associate with IBR 404F orIBR 404H. In such potential association scenarios, the exemplarytopology coordinator at an IBMS Private Server 424 or IBMS Public Server428 can change policies or configuration parameters for such IBRsenumerated above in reference to FIG. 4 such that such IBRs are forcedto associate differently or given an option to associate differently asa localized decision based on certain adverse network conditions such asinterference or link failure.

For embodiments in which the IBMS Private Server 424 or IBMS GlobalServer 428 acts as a topology coordinator, such capability may alsoadditionally or alternatively extend to IBC internal topologycharacteristics such as VLAN port mapping, MPLS routing paths,distribution of traffic to redundant IBR links, etc. again in view ofdesired redundancy, failover or load balancing goals, and applicable SLArequirements including, for example, localized network congestion oraccess cost considerations.

As described in co-pending U.S. patent application Ser. No. 13/212,036,some IBR embodiments use fixed super frame timing parameters.Particularly for Time Division Duplex (TDD) fixed super frame operation,the relationship between start and end of transmission timing in anygiven link direction to other such transmissions by other IBR links innearby geographic proximity can greatly affect both the amount ofinterference experience by such links and the effectiveness ofinterference cancellation techniques at receiving IBRs.

In some embodiments, particularly for situations where TDD fixedsuperframe timing IBR links are deployed, the IBMS Private Server 424 orIBMS Global Server 428 acts as a superframe timing coordinator for anIBS 400 within a given geographic region typically in conjunction withthe RF spectrum coordinator and topology coordinator capabilitiesdescribed above. For example, an exemplary IBMS Private Server 424 orIBMS Global Server 428 with the capabilities described herein maycommunicate policies or configuration parameters to some or all IBRs 404in an IBS 400 such that each IBR 404 is directed to use or to favor theuse of certain super frame timing parameters such as uplink/downlinkduty cycle and super frame timing offset relative to a global timingreference or current local timing reference. Such policies andconfiguration parameters may be determined at exemplary embodiments ofthe IBMS Private Server 424 or IBMS Global Server 428 in view of similarconsiderations described above for the RF spectrum coordinator andtopology coordinator capabilities. For example, in the IBS 400 shown inFIG. 4, any IBRs described above as capable of associating with multipleother IBRs, such as IBR 404D can associate with IBRs 404B, 404C or 404F,are likely to also cause meaningful interference at any such IBRs notpresently associated with. Thus if co-channel operation is required thenadvantageously the exemplary superframe timing coordinator capability ofan IBMS Private Server 424 or IBMS Global Server 428 would setsuperframe timing related polices or configuration parameters tominimize the impacts of such interference as measured or calculated.Alternatively or additionally, the superframe timing coordinatorcapability is invoked in conjunction with the RF spectrum coordinatorand topology coordinator capabilities such that if acceptable IBR linkperformance is deemed unachievable by super frame timing changes thenchanges to policies or configurations parameters for RF spectrum ortopology may be invoked by the IBMS Private Server 424 or IBMS GlobalServer 428.

FIG. 8A illustrates an IBR suitable for obstructed LOS PTP operation (orsector-limited PMP operation) in which spatial diversity (and optionallypolarization diversity and/or pattern diversity) is utilized to theexclusion of directional diversity. As shown in FIG. 8A, all of theantenna elements 804 are positioned on a front facet 808 of the IBR. InFIG. 8A, the IBR 800 includes eight antenna elements 804 (Q=8). It willbe appreciated that the IBR 800 may include less than or more than eightantenna elements 800. Additionally, in some embodiments, a subset of theantenna elements 804 may be used for transmission, while a differentsubset may be used for reception. Alternatively, some or all of theelements 804 may be used for both transmission and reception.

FIG. 8B illustrates another embodiment of an IBR 850 in whichdirectional diversity is present. IBR 850 includes the same number ofantenna elements as the IBR 850 shown in FIG. 8A (Q=8, or 16 if usingcross-polarization feeds to all antenna elements). In FIG. 8B, theantenna elements 854 are arranged on a front facet 858 and two sidefacets 862. In FIG. 8B, the side facets 862 are at a 45° angle in theazimuth relative to the front facet 858. It will be appreciated thatthis 45° angle is arbitrary and different angles are possible dependingon the specific radiation patterns of the various antenna elements.Furthermore, the angle may be adjustable so that the side facets 862 canvary in azimuth angle relative to the front facet between 0° to 90° (anyvalue or range of values between 0° to 90°). Conventionalelectromechanical fabrication elements may also be used to make the sidefacing angle dynamically adjustable by using, for example, servo motors.Additionally, variations of the embodiment of FIG. 8B can use more thanthree facets at different angular spacing all within a nominal azimuthalrange of approximately 180°, and the number of antenna elements 854 maybe less than or greater than Q=8. For example, in one embodiment, theantenna array includes four facets uniformly distributed in an azimuthalangular range across 160°. Additionally, in some embodiments, a subsetof the antenna elements 854 may be used for transmission, while adifferent subset may be used for reception. Alternatively, some or allof the elements 854 may be used for both transmission and reception.

It will be noted by one skilled in the art the geometrical arrangementof the elements 804, 854 in FIGS. 8A and 8B allow the potential use oftransmission and reception beam forming in two dimensions by IBR 800 andIBR 850, which may allow for both vertical and horizontal beam and nullsteering during both transmit and receive processing.

FIG. 9 illustrates a deployment scenario according to one embodiment ofthe invention. Pre-existing CBR 132 a utilizes an unobstructed line ofsight wireless link 136 to CBR 132 b. The CBRs have a relatively narrowbeam (e.g., 3 dB width of 2 Degrees in both azimuth and elevation). Atall building 312 is located between CBR 132 a and CBR 132 b. Thebuilding 312 is short enough that it does not adversely impact link 136because each CBR has a relatively narrow beam.

FIG. 12 illustrates a CBR antenna pattern having a similar main antennabeam width and other antenna pattern attributes as the CBRs 132 a, 132 bof FIG. 9. It is relevant to note that while the CBR antenna patterndepicted in FIG. 12 possesses a narrow 3 dB main beam width 1240relative to the peak gain 1210 in the antenna bore sight direction,there remains the possibility for signal reception from angles beyondthe 3 dB beam width points, but with lesser relative antenna gainlevels. For example, the gain level at twice the 3 dB beam width may beas significant as −10 dB or −15 dB relative to the main bore sight gain1210. Furthermore, the gain at side lobe 1220 remains within −20 dB, inthis example, relative to the peak bore sight gain 1210, and is locatedat roughly 3 times the angular distance from the bore sight direction asthe 3 dB main beam radius. In contrast, antenna nulls, including nulls1230, are points where the residual gain from the CBR antenna is at asignificant minimum level and are generally interspersed between sidelobes or other higher gain portions of the antenna pattern. The antennapattern depicted in FIG. 12 represents a typical CBR antenna pattern,such as one produced by so called parabolic dishes including, generally,a circularly symmetric antenna gain pattern about the bore sight.

As discussed in additional detail in this disclosure and the co-pendingapplications previously incorporated by reference, the use ofmulti-element antenna systems, in some configurations, allows an antennaarray's beams, side lobes, and nulls to be advantageously directed. Bythe advantageous angular placement of an antenna array's main gain lobe,and the placement of lower gain portions of the antenna array's gainpattern in specific other directions, a desired link may be maintainedwhile managing the level of undesired signal transmitted to or receivedfrom other transceiving radios (including CBRs) in the area. The antennaarrays may utilize adaptive techniques incorporating transmission nullsteering or reception null steering approaches. In one embodiment,adaptive antenna array processing, including null steering algorithms,are utilized to allow for the deployment of RE-IBR 920 and AE-IBR 910 ofFIG. 9 in the presence of CBRs 132 a and 132 b so as to not impact theCBRs 132 a,b receiver performance by reducing interfering signal levelsfrom each IBR impinging upon the CBR antenna gain patterns.

In one embodiment, the antenna elements 854 (e.g., utilized by IBR 910and 920) have a 3 dB antenna beam width in elevation (930 and 940,respectively) of 15 degrees and a 3 dB antenna beam width of 30 degreesin azimuth. Such individual antenna pattern radiation patterns may causeinterference to deployed CBRs in the geographic area. In one example,the signal transmissions from RE-IBR 920 to CBR 132 a via propagationpath 960 are received at a sufficient level so as to cause a degradationof the CBR link 136 performance. In another example, a signaltransmitted from AE-IBR 910 along a signal propagation path 970 isscattered from building 312 and received in a side lobe of the antennapattern of CBR 132 b at a sufficient level to also impact the CBR to CBRlink performance.

In one embodiment, the RE-IBR 920 and AE-IBR 910 utilize a multi-elementantenna array such as IBR 850. Such an antenna array configuration allowfor spatial array processing. Such spatial array processing may includephased array processing, digital beam forming, transmission nullsteering, elevation and azimuth beam steering, antenna selection, beamselection, polarization adjustments, MIMO processing techniques, andother antenna pattern modification and spatial processing approaches forboth the transmission and reception of signals. It will be appreciatedthat other antenna array configurations may be used, which have more orfewer antenna elements than IBR 850 and have different geometricalarrangements, polarizations, directional alignments and the like.

Embodiments of the present invention are advantageous because the impactto the CBR link performance can be reduced or eliminated completelywhile allowing for the deployment of the IBR 910 and IBR 920 in the samegeographical region as the CBRs with sufficient inter-IBR link 950performance. In some embodiments, IBR deployments may be enabled in thesame geographical areas and within the same frequency bands, and infurther embodiments such deployments may be in a co-channelconfiguration between CBRs and IBRs, while allowing for sufficientperformance between IBR 910 and IBR 920.

FIGS. 10 and 11 illustrate additional exemplary deployments of IBRs inthe presence of CBRs. FIG. 10 is a side perspective view of elements ofa deployment embodiment example, and FIG. 11 is a top perspective viewof the deployment embodiment. It should also be noted that somegeometrical differences exist between FIG. 10 and FIG. 11 to provideillustrative descriptions. Where FIG. 10 and FIG. 11 are in conflict orotherwise are inconsistent, the differences should be consideredalternative embodiments.

Intelligent backhaul radios RE-IBR 1020 and AE-IBR 1025 are deployedwith configurations as previously discussed in the related embodimentsof IBRs 910 and 920. The IBRs 1020 and 1025 are deployed for cellularbase station backhaul with obstructed LOS propagation link 1060according to one embodiment of the invention.

In FIGS. 10 and 11, CBR A 1005 and CBR B 1010 are deployed for cellularbase station backhaul with unobstructed line of sight (LOS) propagationlink 1015. CBRs 1005 and 1010 are deployed within the same geographicalregion of the IBRs 1020 and 1025. Each CBR 1005, 1010 includes anantenna pattern, with 3 dB main beam width (1007 and 1012,respectively). Additional properties of CBRs 1005, 1010 are, in oneembodiment, the same as those described with respect to CBRs 940 and 930of FIG. 9.

In the embodiment shown in FIG. 10, antenna elements 854 are utilized byIBR 1020 and 1025 and have a 3 dB antenna beam width in elevation of 15degrees and a 3 dB antenna beam width of 30 degrees in azimuth. Suchindividual antenna pattern radiation patterns may cause interference todeployed CBRs in the geographic area. In one example, the signaltransmissions from RE-IBR 1020 to CBR 1005 via propagation path 1030 arereceived at a sufficient level to cause a degradation of performance ofthe CBR link 1015. In another example, a signal transmitted from AE-IBR9025 along signal propagation path 1040 and 1045 is scattered andattenuated from building 1050 but has a sufficiently low level so as tonot cause performance degradation to CBR 1010 or IBR 1025.

As explained above, in FIG. 10, RE-IBR 1020 and AE-IBR 1025 are deployedfor cellular base station backhaul with obstructed LOS propagation link1060. Additionally, with respect to the present embodiments of FIGS. 10and 11, RE-IBR 1020 and AE-IBR 1025 utilize a multi-element antennaarray, such as antenna array 850. The antenna array 850 allows forvarious spatial array processing. As described above, such spatial arrayprocessing may include phased array processing, digital beam forming,transmission null steering, elevation and azimuth beam steering, antennaselection, beam selection, polarization adjustments, MIMO processingtechniques, and other antenna pattern modification and spatialprocessing approaches for both the transmission and reception ofsignals. It should be noted the current embodiment is only oneconfiguration, and that other embodiments may utilize more or fewerantenna elements and with varying geometrical arrangements,polarizations, directional alignments and the like.

Embodiments of the invention relate to determination of IBR networkparameters and the installation and commissioning process of remote endIBRs (RE-IBRs) and Aggregation End IBRs (AE-IBRs). A detailed processfor installing and commissioning the IBRs is described in further detailbelow with reference to FIG. 14 and FIG. 15. These processes and/or someof the process steps may be may be performed using one more of IBRs andIBCs, the IBMS 420, or elements thereof including IBMS Private Server424, IBMS Private Database 432, IBMS Global Server 428, IBMS GlobalDatabase 432, the Private Database 440, and the processing and storageelements accessible utilizing the public internet such as the Cloudcomputing resource 456, Public Database 452, and Proprietary Database.

Embodiments of the invention allow for a practical approach to thedeployment, monitoring and operation of obstructed non-line of sightsystems in the presence of unlicensed or licensed conventional backhaulradios or other licensed services, according to 47 C.F.R. § 101, withinthe same operational bands. Further, such an embodiment allows for therapid deployment of new backhaul radios configured for co-channeloperation with the foregoing systems, including conventional backhaulradio networks and other 47 C.F.R. § 101 systems such as Common CarrierFixed Point to Point Microwave Service and Private Operational FixedPoint-to-Point Microwave Service and associated bands as described in 47C.F.R. § 101.101, and listed in the universal licensing System (ULS)operated by the Federal Communications Commission.

To fully utilize the capabilities of the IBRs and the IBMS, particularlywithin specific 47 C.F.R. § 101 licensed bands, it is advantageous toutilize the IBMS and IBRs to aid in the determination, deployment andmanagement of IBR operational parameters, when IBRs are deployed in thesame bands of operation as existing CBRs 1005, 1010 or other radios towhich or from which interference is undesirable or forbidden. In someembodiments, such deployments may include the co-channel operation withCBRs 1005, 1010 or other systems including 47 C.F.R. § 101 systems, suchas Common Carrier Fixed Point to Point Microwave Service and PrivateOperational Fixed Point-to-Point Microwave Service and associated bands.

During installation or during deployment and operation of the IBRs 1020,1025, the IBS, IBMS and other public and private network elements mayuse information stored with one or more network elements to determine oraid in the determination of IBR operational parameters for allowingco-band or co-channel operation with manageable interference impact toand from CBRs 1005, 1010 or other aforementioned services within ageographic zone, or within a known radio frequency propagation distance.

Exemplary IBR operational parameters include but are not limited to: theselection operational frequencies; the modification of transmitterantenna patterns; the modifying or selection of antenna polarization orspatial patterns; the selection of specific antennas from a set ofavailable antennas; the selection of transmission nulls, reducing theinterference impinging upon other systems; the selection of receiving ortransmission digital beam forming weights, or algorithmic beam formingconstraints; the physical movement, placement, alignment, oraugmentation of one or more antenna elements, or antenna arrays byelectrical, or electromechanical control or by a request for manualadjustment or augmentation during or after installation; and themodification of transmission power; and the selection of interferencemargin values for the reduction of the risk in interfering existingsystems.

In one embodiment, the determination of the IBR operational parametersis performed utilizing an algorithm based at least in part on thelocation of the CBRs 1005, 1010 and radiation parameters. Thisinformation may be stored in the Universal Licensing System (ULS)operated by the Federal Communications Commission (FCC), or on otherpublic or private databases. In one embodiment, ULS information andassociated radiation parameters in combination with radio frequencypropagation models are utilized to determine the level to whichoperation of an IBR, under various IBR operational parameters wouldinterfere with one or more licensed 47 C.F.R. § 101 services, includingCommon Carrier Fixed Point to Point Microwave Service and PrivateOperational Fixed Point-to-Point Microwave Service within FCC designatedbands. In another embodiment, reports of received signal are provided byIBRs, possibly in combination with existing IBR operational parameters,to the IBMS for use in IBR operational parameter determination. Suchreports may be stored by the IBMS and used alone or in combination withCBR radiation parameter information from public or private databases toperform IBR operational parameter selection.

Further embodiments may include an iterative method. For example, theIBRs may report received spectral measurements and configurationparameters to the IBMS, which performs selection of some or all for theoperation parameters, and passing the parameters to respective IBRs. TheIBRs may then perform additional or refined scanning, or initialoperation, prior to the determination of the IBR operational parameters.

In one embodiment, the remote end IBR (RE-IBR) is configured to operatewith the aggregation end IBR (AE-IBR) on one or more frequency channelswhich are co-channel with a TDD CBR. In this embodiment, the AE-IBR hasa wired Ethernet connection to the IMBS. The RE-IBR connects to the IBMSutilizing an out of band data link in the form of a cellular data linkduring configuration, which may be a mobile phone with a Wi-Ficonnection to the RE-IBR (i.e., the phone is acting as a mobile hotspot) or utilizing a Wi-Fi direct connection. Upon initiating theconfiguration process in this embodiment, the respective IBRs perform ascan of their receive channels to detect existing CBRs. The IBRs thenreport their respective antenna configurations and scan results to theIBMS. The IMBS, in one embodiment, will determine, assuming anotherchannel may not be used, the level of interference the CBR will receive.The interference may be determined utilizing IBR effective antennapattern adjustments and, optionally, associated information retrievedfrom a data base of CBR parameters. In some embodiments, the effectiveantenna pattern adjustment include the use of transmission beam nullingfrom the required one or more IBRs to further reduce the interferencelevels which may be received at the CBR, while maintaining a minimumrequired performance between the respective IBRs. In one embodiment, aninterference margin is also calculated. The interference margin is usedas an additional reduction of the required interference to the targetCBR. The interference margin may be based on a fixed amount, a level ofuncertainty of the predicted interference, an amount based upon thereliability or predicted accuracy of interference calculations, or basedupon using or the availability of, or specific values of CBR antenna andoperating transmission parameters retrieved from a database.

In some embodiments, the RE-IBRs and AE-IBRs may operate on channels forwhich no interference is detected, but are within a predetermineddistance of CBRs. The distance is determined based on the geographiclocation of the IBRs and the CBRs. The location of the CBRs may bedetermined by accessing, for example, the FCC (ULS) database. In suchsituations, an interference margin value or other operational constraintvalue may be utilized by the IBMS based upon propagation models, tofurther reduce the likelihood of interfering with the CBR.

In some embodiments, co-existence of the IBRs with FDD CBRs may berequired. In these embodiments, interference margins or operationaltransmission constraints, including transmission beam nulling, may needto be calculated. For example, in one embodiment, the selection of thetransmission antennas to utilize for receive during a scan procedureduring configuration may allow for enhancement of transmit beam formingand transmit nulling operations and may further aid in the determinationof values related to transmission beam nulling.

In some embodiments, received signals transmitted from a CBR 1005operating in FDD are detected during a scan procedure at an IBR 1020.However, the IBR to IBR link, in one deployment, is configured tooperate on the specific FDD paired frequency co-channel used forreceiving by the FDD CBR 1005 as determined the IMBS 420 and FCC database records in a public data base 452. In this embodiment, transmissionbeam nulling weighs for the CBR 1005 receiving channel (uplink pairedchannel used by CBR 1005 for receiving from CBR 1010) or othertransmission constraints may be determined based upon the receivedsignals at the IBR 1020 in the paired (downlink paired channel as usedby CBR 1005 to transmit to CBR 1010) channel, despite the frequencydifference for the transmission channel. Such calculations may utilizepropagation modeling to determine interference levels, reportedmeasurements by the IBR to determine the level of frequency flat fading,and data base values related to CBR parameters. These calculationsinvolve a constrained transmission beam forming calculation for example,including an interference margin based at least in part upon thedetermined level of flat fading of the scanned signal on the pairedband, in this embodiment.

Embodiments of the invention allow for IBR network parameters to beselected to avoid co-channel operation with CBRs. In embodiments whereco-channel operation between the IBRs and CBRs is not avoided or isrequired, the impact on link performance to the CBR 1010 and from CBR1005 can be reduced or eliminated completely while allowing for thedeployment of the IBR 1020 and IBR 1025 in the same geographical regionwith sufficient inter-IBR link 1060 performance. In some embodiments,the IBRs may be deployed in the same geographical areas and within thesame frequency bands as CBRs. In some embodiments, the IBRs and CBRs maybe deployed in a co-channel configuration, while still allowing forsufficient performance between IBR 1020 and IBR 1025.

FIG. 13A is a table of a partial listing for the frequency availabilityfor specific radio services. The listing is replicated from 47 C.F.R. §101.101. In FIG. 13A, frequency band 1305 is listed as operating from3700 MHz to 4200 MHz. Frequency band 1305 is available for CC (CommonCarrier Fixed Point-to-Point Microwave Service) and OF S (PrivateOperational Fixed Point-to-Point Microwave Service).

FIG. 13B is an illustration of an exemplary deployment for occupancy ofservices in the 3700 to 4200 MHZ frequency band 1305 for conventionalcellular backhaul radios or other services as licensed under 47 C.F.R. §101 and listed online in the FCC Universal Licensing System. Theservices deployed within this band may be time division duplex (TDD) orfrequency division duplexed (FDD). FDD systems utilize separatefrequency channels for receiving and transmitted signals to each radio,as shown in FIG. 13B. TDD systems utilize a single frequency channel andalternate receiving and transmission with the radio to which they arecommunicating, allowing for the deployment of such services in thecenter of the operational band, as shown in FIG. 13B.

FIG. 14 is a flow chart showing a process of installing an IBR accordingto one embodiment of the present invention. It will be appreciated thatthe process described below is merely exemplary and may include a feweror greater number of steps, and that the order of at least some of thesteps may vary from that described below.

The installation process may be used for a point to point or a point tomultipoint configuration. In some embodiments, the point to multipointconfiguration includes multiple point to point configurations which areconnected utilizing the IBS. In other embodiments, the digital beamforming capability of the IBRs allows for the same physical antennaarray to be used in a multi-user MIMO or spatial division multiplexing(SDM) approach to support multiple point to point links. In yet otherembodiments, point to multipoint links may be supported utilizing a timedivision multiplexed (TDM) approach, or utilizing frequency divisionmultiplexing (FDM) on a per carrier or sub carrier (OFDMA) approach.

Each of the point to point multiplexing approaches described herein maybe used together or in combination to allow for the support of point topoint and point to multipoint links in various embodiments, and aresupported by the current and alternative embodiments of the processdescribed herein with respect to FIG. 14.

The installation process begins at step 1420. At step 1420, a coursealignment of RE-IBR 1020 of the line of sight or obstructed line ofsight path 1060 to the AE-IBR 1025 to within some angular tolerance(e.g., +/−10 degrees) is performed. This alignment is typically withinthe antenna pattern of the elements of the instant IBR (e.g., the 3 dBantenna gain pattern of antenna elements 854 on the front 858 of IBR850). The course alignment may be physically refined (manually,electro-mechanically), and may be further electronically refined usingantenna beam steering approaches, at later steps as describedhereinafter. The physical alignment may also be aided by an electroniccompass and an application utilizing the geographical knowledge of theinstant IBR being installed and one or more IBRs to which a pint topoint link is to be established. The application may be executed andconfiguration files or other information distributed locally or remotelyby or between any IBS or IBMS network element as discussed with respectto the generation configuration files previously described with respectto FIG. 4. The electronic compass may be integrated with the IBR, orreside within an installation assisting device. The installationassisting device may be a console mode terminal, mobile communicationsdevice, smartphone, tablet, handset or the like and be linked to the IBCor IBR using a Wi-Fi link, a wired cable, or cellular data link.

In some embodiments, the installation assisting device may utilize acellular data connection to connect with the IBMS or other networkelements and to facilitate communication to perform the steps of theprocesses described with reference to FIG. 14 and FIG. 15. In oneembodiment, the installation assisting device is connected to the IBRutilizing Bluetooth or Wi-Fi, and connects to the IMBS utilizing a 3G,4G or other wireless communication link. Embodiments utilizing suchcommunications may act as a conduit by which the IBR is able tocommunicate with elements of the IBMS or other required networkelements.

The installation assisting device may further be mechanically mountableto the IBR antenna array in some embodiments to allow for the use of anintegrated compass in registration to the antenna array bore sightangle. Such an arrangement, in various embodiments, may be utilizedalone, or in combination with another installation assisting device,each integrated with or separate, but in communication with a respectiveIBR, allowing for the course alignment of one more IBRs. Communicationsby and between the installation assisting devices may be direct or maybe the result of interacting with other network elements of the IBSand/or IBMS.

In some embodiments, the IBR may make use of a cellular data link by wayof the installation assisting device or an integrated cellular device.The cellular device may also be operable to interface to the IBRcurrently being installed for the continual monitoring or configurationof various parameters on an ongoing basis. The specific functions of aninstallation assisting device and cellular device may further beintegrated into specific IBRs.

When deploying an IBR in a band and location where no interference toexisting CBRs is possible, mechanical or other alignment may further beperformed utilizing training signals transmitted by one or both of theIBRs. When deploying in a band where CBRs may be possible, precautionsmust be taken to ensure there is no interference with the CBRs. Thedetermination of the existence of CBRs may be performed utilizing aconnection to elements of the IBMS as will be described in furtherdetail below. However, in some embodiments, a provisional interferenceassessment determination may be made in step 1420. Course alignmentsignals may be used if no interference is possible to the existing CBRswithin one or more specific frequency channels based on this provisionalinterference assessment. In some embodiments, a “safe” lower powertransmission at a lower data rate may be used to further ensureacceptable risk of interference with existing CBRs. Safe transmissionsmay be signals with a lower data rate or no data at all (e.g., pilotsignal or symbols), allowing for significantly lower transmission power.The signals may additionally include channel sounding symbols, so as tolater aid in the refinement of link performance and interferenceassessment. For example, in the case of MIMO or MISO transmissions,successive symbols covered by an orthogonal code as used within IEEE802.11n, differing OFDMA pilot symbols from each transmit antenna, Walshor Zadoff-Chu sequences, and the like may be used.

Information received from such sounding signals may be used to evaluatethe diversity benefit of a physical positioning of an IBR antenna array,such as those discussed previously, including the order of the spatialchannel matrix between the two IBRs. Such information may be used withinany of the current and subsequent steps to aid in physical alignment, orconfiguration or selection of specific antenna elements as being used toreceive, transmit or both, and including various polarizations.

In some embodiments, the most optimal course or fine physical alignmentmay not be aligned with or near the bore sight angle as discussedpreviously. Use of sounding signals allows for a more optimal diversityor channel capacity alignment. Additionally, sounding or trainingsignals may be used to evaluate the potential performance of a specificphysical alignment in the presence of an interferer which may beimpactful to the performance of the IBR links. Such evaluation mayresult, in some cases, in an IBR alignment which is neither the nearbore sight alignment, nor the highest propagation based capacity(highest order spatial channel matrix) between the two IBRs. In someembodiments, a more optimal alignment will take into account the desireto not interfere with or to not be impacted by interference fromexisting radio links (such as CBRs or other links) based on scanning forreceived signals or based upon database calculations, or both.

Such sounding or training signals, in some embodiments, may be permittedto be utilized if it is determined that no CBRs are in the area andpotentially impacted based upon such transmissions at specific levels.The transmission levels of such training signals may be adjusted basedupon a calculated propagation distance, or a fixed distance from one orboth of the IBRs, or a frequency separation between the frequenciesbeing sounded, and the operating channels of the CBRs as optionallyretrieved from a database.

A physical adjustment of the initial alignment may be determined to bedesirable if a better alignment is possible or if only a significantlycompromised operation of a IBR to IBR link (e.g., link 1060) ispossible. Such adjustments may be requested to be made manually by theinstaller, in some embodiments utilizing the installation assistingdevice, email, sms, chat, or the like. In other embodiments, physicaladjustments made be made using a control signal to effect a mechanicaladjustment, utilizing an electromechanical approach such as a servomotor, a motorized screw turn, or the like as are known in the industry.

Various embodiments of the preceding physical installation, course andfine alignment process may be used in any combination together orseparately in step 1420 or other steps including step 1460 wherein oneor more IBR network parameters are adjusted including physicalparameters such as antenna placements and alignment. Aspects of thepreceding embodiments may also be used during step 1470, such as theperforming RF channel scanning for CBRs, the use of channel sounding andalignment signals including “safe” alignment signals when in thepotential or actual presence of CBR links or interferers, or for thedetermination of the satisfactory performance of the currently set IBRnetwork parameters. Adjustment to the antenna array placement IBRnetwork parameters may further include adjustments in elevations,azimuth, polarization, physical configuration or antenna elements,addition, removal, or re-placement of operational transceivers orassociated antenna elements collateral to the integrated antenna arraysof IBR electrical down tilt. One such electrically controllable downtilt product on the market is the Andrew Teletilt RET system(http://www.commscope.com/andrew/eng/product/antennas/teletilt/index.html>).Other products may peform electrical or manual adjustments to theazimuth pattern of the antenna elements or pattern. It will beappreciated that some of the antenna alignment parameters are notdynamically adjustable; instead, the parameters are static orsemi-static parameters, which are generally static and set atinstallation, or, optionally, reconfiguration.

Upon completion of the initial Physical Installation step 1420, theprocess continues to step 1430. At step 1430, the instant IBR performsscans for received signals within the bands of interest. Such signalsmay include specific signals from CBRs or other § 101 licensed radiolinks, or may additionally include detection of other non-CBR or § 101licensed links, such as other IBRs or other radios in the band operated.The scans performed by the IBR being installed, or other IBRs by tuningtheir receivers to one or more of the desired operating frequencieswithin one or more bands. The scans may include varying bandwidths, orbandwidth specific to the detection of specific signals of interest. Thescans may further utilize generic detection approaches including simplepower detection, or RSSI, or detection techniques specific to signals ofinterest such as preamble, pilot tone, pilot symbol, training symbol,periodicity, or symbol rate correlations or properties. Additionally,potential guard channels, frame rates, duplexing properties, modulationformats or other system configuration features of known signals may beexploited during or subsequent to the scans to perform detection oridentification of CBRS or other radios, including other IBRs. Scans mayadditionally monitor varying bandwidths and signal channel widths asconfigured in embodiments. In other embodiments, a priori known signaltypes and known or typical signal attributes may be specificallysearched for, or utilized to aid in the search and detection process, orgeneric signals or both may be searched for within the scan. Such apriori signal attributes, as discussed above, may further includetechniques specific to waveforms, or may simply detect power levels in aband.

If available, scans may use information of possible interferers storedor provided to the IBR or configuration device potentially using a datalink to query an FCC data base or IBMS, or other database, or even alocally stored database. Such steps will be further described in step1440, and may be performed jointly, separately, or interactively anditeratively between scan step 1430 and IBR to IBMS connection step 1440,in various embodiments. When data of possible interferers or CBRs isknown to the IBR, or types of possible signals are known to the IBR,differing types of scans may depend upon the expected signals within thearea being FDD or TDD, or the known attributes of the signal includingbandwidths, and typical or known channels or operation of sites within aspecific range, or potential signal propagation distance.

In some embodiments, an initial preliminary and more course scan may beperformed, and additional scans may be performed later based uponinteractions with the IBMS and/or external databases.

Following the completion of the scanning process, or a part of ascanning assignment, a report may be prepared with the findings of thescans included. Such data may be stored locally as a table or otherstructure. Such report or data may be sent to other devices or networksnodes.

The scan reports may include additional data, such as, for example,current IBR or IBC configuration parameters, including antenna, oralignment parameters, location, radio configuration, firmware revisions,and the like.

In some embodiments, the reports contain RF environmental parametersincluding but not limited to: received power levels, spectrum analysisresults, frequencies with receiver power levels, angle of arrive vsreceived power levels, lists of detected signals or a list offrequencies or identifier signals with one or more associated signal RFparameters. Examples of the associated signal RF parameters on a perfrequency or signal basis include but are not limited to: bandwidth,power level, angle of arrival, power levels verses time, antenna weightsused for receiving or nulling the signal, time domain samples of thesignal received on each of a number of the IBR antennas, frequencydomain data vs time, RF channels, and the like.

The data may be stored locally and initial reports and/or data sent tothe IBMS. Optionally, additional reports and/or data may be sent inresponse to requests for specific additional data to conserve timeand/or data bandwidth.

The process continues at step 1440. At step 1440, the IBR utilizes adata link to connect to another network element and performs a query tothe node, or requests processing from the node. In one embodiment, thenode is within the IMBS. The data link may be internal to the IBR, or itmay be an external link (e.g., installation assisting device or othercellular data device). As such, the data link may be permanentlyavailable to the IBR, or may be available temporarily duringinstallation only. In other embodiments, the data link may be initiallya separate cellular data link in a first query, and then be a linkutilizing a connection to another IBR as an in band of operationoverhead messaging embodiment.

As discussed previously, the “safe” alignment signal may also include adata link component allowing for such connections and potentiallyoperating as the IBR to IBR data link with conservative parametersallowing for lower data rates, and reduced risk of interference untilsuch a time as additional processing may be performed. It will beappreciated that additional scanning steps and/or other processing stepsfor further link optimization may be performed.

In some embodiments, the node is a public or private data base, or othercomputing resource which may comprise a cloud computing resource. Inother embodiments, a database query is performed and data returned tothe IBR or other resource local to the IBR to perform processing incombination with the scan results.

At step 1440, the IBMS receives a scan result from the IBR, and storesthe data in a database. The IBR may also provide information about theIBR itself, including, for example, the location of installation of theIBR, angle and azimuth of initial or current antenna array placement,types of antennas (antenna configuration, and patterns in elevation andazimuth), operational frequency capabilities, firmware revisions,sensitivity of receivers, receiver selectivity, transmitter spectrum,transmitter and receiver beam steering or nulling capabilities, radiotransmission power capabilities and adjustment ranges, and the like.

Prior to step 1450, in some embodiments, the IBMS may collect furtherinformation. In these embodiments, the IBMS performs or requests acombination of processing steps and database queries (both or eitherinternal or external to the IBMS). Such queries may include private orpublic databases, and include data associated with 47 C.F.R. § 101licensed radios, and associated links, including CBRs. In someembodiments, the database is the public FCC database which includes, forexample: parameters of CBRs or other operating radio links. Theparameters may be stored in the FCC Universal Licensing System andassociated with Common Carrier Fixed Point to Point Microwave Service.

In one embodiment, the information collected by the IBMS includes, forexample: the location of transmitter and/or receiver (lat/long), boresight angle (magnetic or true north) of any directional antennasincluding fixed dish antennas typical, maximum transmit power, typicaltransmit power, frequencies of operation, height, size, gain, or radiusof antennas or other key operation parameters of the antennas,modulation format, receiver sensitivity, equipment in use at the site,frequencies of operation, channel bandwidths, duplexing method (TDD vsFDD or other future approaches) and, any other or substitute parametersrequired for signal propagation analysis.

In some embodiments, steps 1420, 1430, and 1440 may be modified inorder, combined in various manners, or performed jointly or iteratively,so as to facilitate the additional embodiments and efficiencies.

The process continues at step 1450. At step 1450, CBR Impact andOperational Performance Analysis Processing is performed. In oneembodiment, the IBMS (either directly or using other computingresources) determines the best channels of sufficient bandwidth,resulting in desired performance while not interfering with existingCBRs. In other embodiments, the processing may be performed jointly withthe IBR, or local to the IBR alone. In some embodiments, the CBR impactand performance analysis utilizes data required to perform a signalpropagation analysis utilizing one or more of the parameters retrievedfrom the data base relegated to 47 C.F.R. § 101 fixed microwave point topoint services or other wireless stations, antenna configuration, andpatterns in elevation and azimuth, and any of the aforementioned otherparameters having been received by the IMBS or collected by the IBRs inthe IBS.

In some embodiments, the processing may include performing propagationanalysis based on the IBR parameters, the scan result(s), and/or thecontents of the database(s). Additionally, the IMBS may include storedresults from other scans performed by other IBRs within the IBS. The CBRparameters and the parameters associated with the IBR being installedare used in the processing modeling steps. The collective data andprocessing allows for signal propagation analysis. In some embodiments,the analysis allows for the prediction of the level of interferencewhich the CBRs will receive, and the performance between the obstructedline of sight link between the instant IBR being installed, and therespective IBR participating in the link. In some embodiments, theprocessing includes incorporation of the capabilities of the respectiveIBRs, including their respective operational frequencies, receiversensitivity, antenna configuration, and patterns in elevation andazimuth. Further, the propagation analysis may be utilized to determinethe impact of IBR transmissions on existing CBRs with specific IBRtransmission antenna patterns, frequencies of operation, transmit beamnulling from the IBRs. The knowledge of the type of CBRs deployed (e.g.,FDD vs. TDD) in combination with the scans allows for operationalinterference margins to be utilized to ensure low risk of impact toCBRs. The operational interference margin is utilized to constrainoperational parameters of the respective IBRs such as, for example,power transmitted at a specific frequency channel, in a specificdirection. The constraints may be directly provided to the IBR, or beutilized in the development of the IBR parameters for use by the IBRs.

FIG. 15 illustrates further details of the process of steps 1450 and1460. In particular, the process of FIG. 15 allows for the adjustment ofIBR network parameters such that degrees of freedom of IBRs are utilizedto mitigate the impact to existing CBRs and interference from anyexisting other radios, and ensure satisfactory performance of theobstructed or unobstructed line of sight IBR point to point or point tomultipoint links. Additional details will be discussed in further detailwith reference to FIG. 15.

The degrees of freedom may be adjusted utilizing transmittable IBRparameters or configuration settings. In one embodiment, manualadjustment the IBR configuration may be requested, if the modelingalgorithms determine that the configurable degrees of freedom (e.g.,frequency channels of operation, transmitter beam former nulling, andantenna selection) have been exhausted and the link performance is notsufficient. Such adjustments, as previously described, may be performedby electromechanical approaches or as a physical adjustment by theinstaller or technician. Additionally, during installation, adjustmentby a servo motor or other motorized approach may be performed by atemporarily installed adjustment device, including such motorizedadjustment capabilities, and reusable during other installations. Insuch an embodiment, a permanently installed adjustable bracket may beused, and secured so as to securely fix any further movement of theantenna array, prior to removal of the temporary adjustment device.

Further manual IBR degrees of freedom modification requests may includean installation of additional transceivers of the IBR to allow foradditional transmitter nulling degrees of freedom to create sufficientnulling capability. In one embodiment, the additional one or moretransmitters may be integrated together with the IBR within a panel suchas 858 or 862. In other embodiments, one or more additional transmittersmay be separate from the IBR panels and adjusted in another directionallowing for new “sub array” processing, or additional nullingcapability in a new azimuth, elevation, or frequency.

In other embodiments, the additional degrees of freedom may be createdby the addition or relocation of transceivers or receivers. Inembodiments where new or adjusted receiver capability degrees of freedomare provided, additional immunity to the interference from other radiosis possible, or an increase in the performance of the point to point IBRlink is possible in same or other embodiments. Algorithmic parameters asused in receive or transmitter beam forming techniques are furtherdescribed in co-pending patent application Ser. No. 13/212,036, entitledIntelligent Backhaul Radio, incorporated herein by reference and furtherdetailed in relation to FIG. 15.

With reference back to FIG. 14, the process continues at step 1460. Atstep 1460, the IBR network parameters are provided to the respectiveIBRs utilizing any of the previously described approaches in variousembodiments (e.g., using a separate cellular data link providingconnectivity between an installation assisting device the IBMS and theinstant IBR, or an existing data link between the instant IBR and theIBMS via an IBC). The IBR makes adjustments based on the IBR networkparameters received from the IBMS.

The process continues at step 1470. Step 1470 is similar to step 1420 inthat a scan is performed. The scan of step 1470 may be a scan withmodified scanning parameters to provide more detail related to a signalof interest such as detected in a previous scan, by another IBR, or as apredicted CBR from the database or other approaches providing data knownto the IBMS. The IBMS may request that the scanning parameters bemodified to provide more detail related to a signal of interest such asa detected or predicted CBR from the database or other scans known tothe IBMS.

In some embodiments, the IBR may perform rescanning, sounding, or otherattributed assessment techniques as a result of physical adjustmentsmade to the configuration of an IBR, relative to antenna positioning,repositioning, addition or removal, as required. In the case where aphysical reconfiguration of an IBR due to a readjustment or othermodification of antenna positioning the scans may be limited and moredetails to a specific frequency range, angular range, azimuth range, orother scanning dimensions. Other reconfigurations may be required toincrease the degrees of freedom within the operating environment resultin the need for additional scans.

In some embodiments, transmission of a signal may be used to aid in thedetermination of the link performance between respective IBRs, includingany specific transmission beam form nulling constraints required by theenvironment. Such transmission provides input to step 1480. Examples ofthe test transmission signals include an estimation signal, channelsounding signal, alignment assistance signal, safe data link signal, orthe like. The test signal may be used to further evaluate the IBR linkor environment, utilizing the current IBR network parameters, optionallyincluding the use of modified frequencies of operation, transmissionnull steering to existing CBRs, and/or alternative antenna selections.Other embodiments utilize modeling of propagation to determineperformance goal satisfaction in step 1480.

In some embodiments, the parameter modifications may be a request foradditional scans to be performer in mode details relating to specificfrequencies or signal detection attributes for instance. In otherembodiments, the updated IBR network parameters may include extensivemodifications to the operation of the individuals IBRs including anycombination of techniques determined by the parameters discussed herein.

Upon the determination that the new IBR to IBR unobstructed line ofsight link is determined (in 1480) to meet performance as discussed, theprocess of FIG. 14 is exited in step 1490. The performance goals in someembodiments include a minimum data rate between two respective IBRs(MBPS), a minimum reliability parameter such as frame error rate (FER)or bit error rate (BER), an acceptable CBR interference tolerance andparameter in dB as determined by either calculation, extrapolation,modeling, or direct measurement, together or in combination. Suchinterference assessment margin approaches may include a factor formeasurement, or prediction margin of error when direct measurement isnot possible.

As an example, in the case where a time division duplexed protocol CBRis detected, and known parameters relating to the CBR transmission powerare known as a result of access to a database, the reciprocalpropagation channel characteristics of time division duplexed signalsmay be utilized to determine potential IBR interference with arelatively low margin of error. In other embodiments, where the CBR is afrequency division duplexed signal, use of one, several or all of theperspective IBR transmitter antennas, configured temporarily fortransmission from those specific antennas to interfere with the CBR onthose specific frequencies, using the channel reciprocity, which alsohas a relatively low margin of error.

In embodiments where only one side of a link is detectable due toblockage from the transmission of one CBR or a receiving CBR, the marginof error may be higher, requiring the use of measurements on onefrequency channel, and prediction on the paired channel. When it can bedetermined that the fading profile across the band is flat due to littledelay spread, a relatively lower margin of error may be utilized. Whenthe delay spread of the channel form the observable CBR is higher indelay spread, resulting in more frequency propagation variation (i.e,frequency selective fading) is present, a higher margin of error isfactored in. In either case, some embodiments may use the transmissionantenna to perform a receive scan during such assessment as perform instep 1470 and evaluated in step 1480. As such, the satisfactoryconfiguration determination of step 1480 may include a measurement ofthe channel variation in frequency or time to determine, at least inpart, the interference error margins.

With reference to FIG. 15, a detailed process for determining theparameters for adjustment is shown. The process may use informationdetermined using one or more steps of the process of FIG. 14. Similarly,the process of FIG. 15 may supply information to one or more steps ofFIG. 14. The process and/or process steps of FIG. 15 may be performed atone or more of the IBR (404, 1020, or 1025), the IBC (408), the IBMS(420), elements of the IBMS (e.g., 424, 428) or another network node(such as a remote processor, or cloud computing resource 456), withinthe foregoing installation assisting device, etc.

The process begins at step 1520. At 1520, IBS performance prediction andassessment, CBR interference impact assessment, and/or CBR interferencemargin factors are determined. In some embodiments, RF propagationanalysis is used to make these determinations. As discussed in FIG. 15,and in additional detail herein, IBRs and/or databases provide input tothe IMBS that can be used in the process of FIG. 15. Examples of thisdata include, for example:

-   known location of the IBRs being installed;-   angle and azimuth of initial or current antenna placement;-   types of antennas (Antenna configuration, and patterns in elevation    and azimuth);-   IBR Operational Frequencies;-   IBR Sensitivity of receivers;-   IBR Transmitter spectrum;-   IBR Transmitter and receiver beam steering or nulling capabilities;-   IBR Radio tx power;-   and other parameters of the IBR.

In step 1520, a CBR interference assessment within a conservative rangeis performed. This range determines specific other stations of interestand may be determined by a fixed geographical range (e.g., 25, 50, or100 miles), or may be a range calculated based on the above parametersand calculations related to the potential for interfering with otherstations. In some embodiments, the potential for interfering with otherstations is determined based on the worst case height of CBR antennas.In other embodiments, the range is calculated based upon a calculatedpotential to be interfered with by other stations based upon a knownworst case transmission power for FCC limits, or other known limits suchas industry commercially feasible limits and the sensitivity of theIBRs, as one example.

Following the determination of a range, stations of interest aredetermined using an FCC database of licensed § 101 fixed microwaveservices point to point stations. Other stations may be determined basedon additional or alternative databases.

In the embodiment where CBRs are of concern, each station of interest isreviewed and the FCC database RF parameters reviewed relative to thepotential to interfere with those stations based on the parameters, orto interfere with the IBRs based upon the existence of those stations.

Exemplary data retrieved from the FCC database (FCC Universal LicensingSystem—http://wireless.fcc.gov/uls/index.htm?job=home) or a cached imageof the database and data from other databases include:

-   Service Group: Microwave Site-Based-   Radio Service Group (including in some embodiments CF—Common carrier    Fixed Point to Point Microwave, and other groups as defined in FIG.    13A)-   Fixed Transmit Location Details-   Location: Lat Long, Street Address-   Support Structure Type-   Site Elevation-   Antenna Elevation-   Transmitter antenna height-   Polarization-   Beam width-   Antenna pointing Azimuth and Elevation Angle-   Antenna Gain in dBi-   EIRP (e.g., 44.8 dBm)-   Frequency and tolerance-   Emission Designator (Equipment Modulation type and rate) for    instance-   Baseband Digital Rate 44736 (kbps), 4 FSK-   Equipment Manufacturer (indicating channel selectivity for including    in calculations in some embodiments)-   “Paths” frequencies of operation-   Location 2: Receive Location—Lat Long, Site Elevation

The determination of interference potential to or from the CBRs mayutilize propagation modeling. While embodiments may use variouspropagation modeling approaches, exemplary propagation analysis modelsinclude:

-   Lee-   Hata-   Okumura-Hata-   ITU-R P.53-   ITU-R P.154-   ITU-R P.452-   ITU-R P.1410-   Ray tracing, flat models, or other models

The models, in some embodiments, are used to perform prediction ofinterference to the licensed CBRs. Such calculations may additionally beused to refine the scanning procedures of FIG. 14, and performinterference model validation by comparing the FCC database predictedand modeled interferers, with the results of IBR scans. In the case ofFDD systems, the modeling to determine interference may be critical,resulting in a varying interference margin tolerance based on directlyobserved, indirectly observed, or predicted but not observed signals,individually or together.

Further determination of interference from other stations may beperformed using reports from other IBRs and use of the propagationmodels and relative “performance margins” to ensure reliability in thecase of uncertain interference levels.

At step 1530, a determination of a predicted satisfactory achievement ofthe system requirements is performed. The criteria used to determine thepredicted satisfactory achievement is similar to those of step 1480 ofFIG. 14. The determination is unsatisfactory if the risk of interferingwith a § 101 radio (CBR or other) is too high, as denoted by a requiredinterference margin of error as discussed, or the risk of beinginterfered with at an IBR is too high such that it is likely that thelink performance will be unacceptable, or if the predicted linkperformance is too low given required constraints and margins. Further,if no frequency channels are available or currently assigned to a IBR,the result is deemed unsatisfactory.

The IBR network parameters are deemed to be satisfactory if the risk ofimpacting a CBR is beyond a determined desired tolerance or interferencemargin, including additional margins for error of prediction in someembodiments. Other embodiments include an acceptable risk of linkoutages acceptably low at a given target performance level (data rate,FER, and/or BER).

If, in step 1530, the process determines that the current IBR Networkparameters are unsatisfactory, the process continues to step 1550. Atstep 1550, one or more degrees of freedom for one or more specific IBRsare modified to satisfy the requirements of step 1530. Examples ofspecific degrees of freedom available at a IBR include:

-   -   perform IBR to IBR Dynamic Frequency Selection to avoid any        operating channels or guard bands where interfere to another        station would be impactful or of minimum impact to the criteria        of step 1530;    -   perform IBR Effective Pattern Adjustment, which in various        embodiments may include Elevation Steering, Transmitter Beam        Nulling and other RF or Digital Array techniques;    -   perform beam forming calculations for use with the antenna        system requiring the generation of Interference Angle of Arrival        Vectors based on non-directly detected sources (e.g., databases,        remote sensing from other IBRs, etc.);    -   perform antenna selection, such as the selection of antenna        elements from differing angular patterns based upon differing        facets of IBR 850, or alternative polarizations;    -   perform transmitter power adjustments;    -   request for Physical Adjustments (Manual, or Automatic), as        discussed elsewhere.

In one embodiment, step 1550 includes performing the following steps.First, dynamic frequency selection is performed. Dynamic frequencyselection predicts interference potential to select a subset of channelswithin desired operating band. Next, if possible, a channel/antennaselection combination is selected within the operating band where thereis no potential of interfering with § 101 links based on propagationpredictions and no interferers to the IBRs have been detected. If nosuch condition exists, the channel/antenna combination is selected withthe combination of an acceptable impact risk, lowest interferencesusceptibility risk, and using Tx effective pattern adjustment. Thesetechniques are then employed in a specific order of optimization,including elevation steering, transmitter beam nulling, any additionalantenna selection options, then transmitter power adjustments. If allthe previous options of the current embodiment have failed to satisfythe link and interference requirements from step 1530, then the channelwith the most acceptable interference susceptibility risk and predictedand manageable risk of interfering with § 101 radios is selected. Next,if all the previous options of the current embodiment yieldunsatisfactory results, antenna transmitter location or angle or azimuthadjustment (manual or mechanically or electrically controlled andautomatized) is requested. Finally, if all the previous approaches havefailed to result in satisfying the criteria of 1530, additional degreesof freedom in the form of additional transmitter or transceivercapability (co-arrays), separate nulling antennas, cancelingtransmitters/arrays, and the like, are requested. The process thenreturns to step 1520. It should be noted that in an embodiment of FIG.15, following the change of an IBR parameter, also referred to as adegree of freedom in step 1550, returning to steps 1520 and 1530 allowsfor the evaluation of each modified parameter and the determination ofsatisfactory configuration per the goals of the system.

As previously described, one approach to the modification of aneffective antenna radiation pattern adjustment is the employment ofdigital beam forming techniques. As such techniques are digital innature, being performed at base band, the receiver and transmitterradiation patterns may differ. In some embodiments, when the sameantennas are utilized for receive and transmit, the effective patternsmay also differ due to differences of digital weightings on the receiverand the transmitter processing. In additional embodiments the weightingmay be the same. In some embodiments, the transmitter and receiverweights may be or be related using a mathematical relation, with thegoal of resulting in differing performance criteria, or in compensatingfor differing receiver and transmitter configurations. In someembodiments, the differing criteria may be to utilize transmit nullingto minimize the transmitter signal in the direction of another receiversuch as, in one embodiment, a CBR or other radio. In other embodiments,the differences in the weights may compensate for the differences inoperating frequency between the receiver and the transmitter, thedifferences between the geometry, polarization, radiation pattern orother properties of the transmitter array relative to the receiverarray, or other factors causing a difference in receiver to transmitterweight applicability. Such techniques may be utilized together,separately, or in any combination. Such a relation has been described asa mathematical function based on differences between the receiverproperties and the transmitter properties or even as a function of thetopology of the IBS deployment, including in certain embodiment theexistence of TDD or FDD CBRs.

Algorithms for the calculation, or the modification of the digitalweights, are known in the art, and may include in certain embodimentsconstraints to modify resulting weights to achieve transmit nullsteering, or receiver null steering. In other embodiments, thealgorithms are unconstrained. Additional beam former algorithms may beemployed for transmitter and or receiver optimization, or forinterference mitigation as known in the art, and include adaptive beamforming techniques. Exemplary beam former or other array processingalgorithms include, for example: MMSE, LMS or RLS, CM, ConstrainedOptimization Techniques, GSC—Generalized Side lobe canceler, a nullsteering beam former, Zero-Forcing Precoding, Dolph-Chebyshev basedtechniques, MU-MIMO like techniques, Schelkunoff Polynomial Methods, andDirty Paper Precoding (DPC).

In the case of transmitter nulling, the determination and estimation ofinterfered channel state information based on received interferingsignal may be employed, and include utilizing the stationary nature ofthe CBR to IBR channel, or compensating for channel variations. In otherembodiments, factors may be considered such as delay spread and spectralflatness.

As will be appreciated, when calculating transmitter weights based uponreceiver weights, differences in the configuration of the transmitterand receiver antenna arrays or transceivers are considered. In the caseof TDD, the reciprocity of the propagation channel may be utilized.However, array calibration should be performed if different antennas areused for receive and transmit. Other factors which should be considered,calibrated, or otherwise compensated for include weighting translationbased on one or more of differing element patterns, gain, phase andpolarization differences, and changes relative to the angle of arrival.Additional factors that should be considered include the differences inantenna array geometries or array factor based on angle dependent mutualcoupling, or other factors.

Transmitter nulling techniques may further be addressed on a per signalof interest basis, such as a CBR, and utilize nulling vectors for use ina constrained optimization or other approach to the determination oftransmitter weights.

Further optimization constraints may include the geometrical translationof nulling vectors and weights on a per SOC basis, a “over constrained”or multiple constrained approach, and, in some embodiments, basingconstraints on differing tolerances for the interference margin oferror. One embodiment may employ generalized MMSE or LMS withconstraints based on tolerance dependent signal of interest (CBR)interference vector constraints (translated) as a function ofuncertainty factors.

The aforementioned techniques may also apply to FDD systems in certainembodiments, including the requirements to compensate for differencesbetween the receiver and transmitter antenna elements. In someembodiments, the difference in frequency results in differing effectivearray geometry as well in terms of the antenna element spacing relativethe operating frequency wavelength. Further, where differing antennaelements are used, differences in the effective geometry result as well.These geometrical differences may be compensated for by adjustments inthe weights utilized on the transmitter, relative to the receiver basedupon expected gain and phase differences relative the geometricaldifferences as measured in wavelength.

One or more of the methodologies or functions described herein may beembodied in a computer-readable medium on which is stored one or moresets of instructions (e.g., software). The software may reside,completely or at least partially, within memory and/or within aprocessor during execution thereof. The software may further betransmitted or received over a network.

The term “computer-readable medium” should be taken to include a singlemedium or multiple media that store the one or more sets ofinstructions. The term “computer-readable medium” shall also be taken toinclude any medium that is capable of storing, encoding or carrying aset of instructions for execution by a machine and that cause a machineto perform any one or more of the methodologies of the presentinvention. The term “computer-readable medium” shall accordingly betaken to include, but not be limited to, solid-state memories, andoptical and magnetic media.

Embodiments of the invention have been described through functionalmodules at times, which are defined by executable instructions recordedon computer readable media which cause a computer, microprocessors orchipsets to perform method steps when executed. The modules have beensegregated by function for the sake of clarity. However, it should beunderstood that the modules need not correspond to discreet blocks ofcode and the described functions can be carried out by the execution ofvarious code portions stored on various media and executed at varioustimes.

It should be understood that processes and techniques described hereinare not inherently related to any particular apparatus and may beimplemented by any suitable combination of components. Further, varioustypes of general purpose devices may be used in accordance with theteachings described herein. It may also prove advantageous to constructspecialized apparatus to perform the method steps described herein. Theinvention has been described in relation to particular examples, whichare intended in all respects to be illustrative rather than restrictive.Those skilled in the art will appreciate that many differentcombinations of hardware, software, and firmware will be suitable forpracticing the present invention. Various aspects and/or components ofthe described embodiments may be used singly or in any combination. Itis intended that the specification and examples be considered asexemplary only, with a true scope and spirit of the invention beingindicated by the claims.

The invention claimed is:
 1. A method for installing a fixed wirelessaccess link between a first fixed wireless access radio and an at leastone second fixed wireless access radio, wherein each one of the firstfixed wireless access radio and the second fixed wireless access radiocomprises at least an antenna array comprising at least a plurality ofdirective gain antenna elements, and wherein each directive gain antennaelement is couplable to at least one receive RF chain or transmit RFchain, said method comprising: course aligning a physical configurationof the first fixed wireless access radio or an arrangement of theantenna array within the first fixed wireless access radio; coursealigning a physical configuration of the second fixed wireless accessradio or an arrangement of the antenna array within the second fixedwireless access radio; transmitting at least one alignment signal fromthe first fixed wireless access radio using a first transmit antennapattern or receiving in order to detect at least one alignment signal atthe first fixed wireless access radio using a first receive antennapattern; transmitting at least one alignment signal from the secondfixed wireless access radio using a second transmit antenna pattern orreceiving in order to detect at least one alignment signal at the secondfixed wireless access radio using a second receive antenna pattern; andone or more of: fine aligning the physical configuration of the firstfixed wireless access radio or the arrangement of the antenna arraywithin the first fixed wireless access radio; and fine aligning thephysical configuration of the second fixed wireless access radio or thearrangement of the antenna array within the second fixed wireless accessradio.
 2. The method of claim 1, further comprising: scanning aplurality of radio frequency channels for detection of radio signalstransmitted from one or more other radio systems, thereby generatingscan data; generating a scan report based on the scan data; andtransmitting the scan report to a server.
 3. The method of claim 1,further comprising: adjusting, upon a detection of at least onealignment signal at either of the first fixed wireless access radio orthe second fixed wireless access radio, one or more of: the firsttransmit antenna pattern; the second transmit antenna pattern; the firstreceive antenna pattern; and the second receive antenna pattern.
 4. Themethod of claim 1, wherein prior to the detection of at least onealignment signal at either of the first fixed wireless access radio orthe second fixed wireless access radio, the first transmit antennapattern is the same as the second transmit antenna pattern.
 5. Themethod of claim 1, wherein prior to the detection of at least onealignment signal at either of the first fixed wireless access radio orthe second fixed wireless access radio, the first transmit antennapattern is the same as the first receive antenna pattern.
 6. The methodof claim 3, wherein the adjusting of one or more of the first transmit,second transmit, first receive, and second receive antenna patternscomprises one or more of: adjusting an effective radiation pattern of anantenna array; selecting one or more ones of a plurality of directivegain antenna elements; steering an effective radiation pattern inelevation; and steering an effective radiation pattern in azimuth. 7.The method of claim 6, wherein the adjusting the effective radiationpattern comprises: calculating digital beam former weights based upon atleast one constraint related to a potential of interference or animprovement of link performance; and applying the digital beam formerweights.
 8. The method of claim 1, wherein either or both of the coursealigning steps utilizes at least one GPS location or compass direction.9. The method of claim 8, wherein at least one GPS location or compassdirection is determined by an installation assisting device.
 10. Themethod of claim 1, wherein at least one of the pluralities of directivegain antenna elements comprises a first subset of one or more directivegain elements with a first polarization and a second subset of one ormore directive gain elements with a second polarization, and wherein thefirst polarization is orthogonal to the second polarization.
 11. Themethod of claim 10, wherein the first polarization is vertical and thesecond polarization is horizontal.
 12. The method of claim 1, wherein atleast one of the pluralities of directive gain antenna elementscomprises at least one patch antenna element.
 13. The method of claim 1,wherein at least one transmit RF chain comprises at least a vectormodulator and two digital to analog converters.
 14. The method of claim1, wherein at least one receive RF chain comprises at least a vectordemodulator and two analog to digital converters.
 15. The method ofclaim 1, wherein either or both of the course aligning steps comprisesat least manually adjusting a bracket.
 16. The method of claim 1,wherein either or both of the fine aligning steps comprises at leastphysically moving one or more of a plurality of directive gain antennaelements by electrical or electromechanical control.
 17. The method ofclaim 1, wherein the alignment signal comprises at least one of anorthogonal code, a Walsh sequence or a Zadoff-Chu sequence.
 18. Themethod of claim 6, wherein the selecting of one or more ones of theplurality of directive gain antenna elements comprises selecting one ormore of: directive gain antenna elements with different angularpatterns; and directive gain antenna elements with differentpolarizations.
 19. The method of claim 1, wherein the detection of atleast one alignment signal at either of the first fixed wireless accessradio or the second fixed wireless access radio comprises at least oneof detecting a preamble, a pilot tone, a pilot symbol, a trainingsymbol, a periodicity, or a symbol rate correlation.